- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: i-node edit recovery plan
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 07:22 AM
07-17-2003 07:22 AM
We have a filesystem that contains corrupted data in the form of three files.
The "corrupted" filenames appear as /mount/dir1/dir2//mount/dir1/dir2/file1
Note the double // , the actual filename as the system sees it is "/mount/dir1/dir2/file1" the PATH to the file is /mount/dir1/dir2
Anyway, with some HP supplied documentation (we were previously supported), I plan to edit the i-node table tonight to remove these anomalies.
The LV the data is located on is NOT in VG00
It is in a mirrored 50GB LV that is the sole member of VGMAT
Question:
Can I unmirror the lv, do the inode edit, and if something goes awry, use the secondary disks to recover from?
(I DO have a tape backup but it would take hours to restore.)
IE: Can I vgexport AFTER the unmirror. and use the secondarys with vgimport?
OR
Could I place the secondaries where the primarys were and just remount?
You might ask, "How did this happen"?
A new datawarehouse API accessing an older "unsupported" version of the Db.
NO it was not me.......:) God bless the industrious user....
Any suggestions are greatly appreciated.
Thanks , ~jdk
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 07:34 AM
07-17-2003 07:34 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 12:19 PM
07-17-2003 12:19 PM
Re: i-node edit recovery plan
After the i-node edit, I need to duplicate the warehouse install on another box.
Would an unmirror, then a VG export, then take the previously mirrored set (along with export file) to the new box for a vgimport work?
Thanks, ~jdk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 12:54 PM
07-17-2003 12:54 PM
Re: i-node edit recovery plan
As was sayed the lvsplit will split then you
can do the fix and you can mount the
other lv from the split and continue to work
til you will fix the disk and made marge back.
This way your users will work.
Caesar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 12:59 PM
07-17-2003 12:59 PM
Re: i-node edit recovery plan
dd if=/dev/rdsk/c5t6d0 of=/dev/rdsk/c6t6d0 bs=1024k
(of course set if= and of= to the proper source and destination drives)
for each physical drive in the volume group.
This does assume that the drives are identical in size.
The idea is after unmirroring, we are going to make exact copies of to disks to the former mirror physical disks. You can then remove the copies and do a vgimport on the new box.
You can then activate the vg on both boxes and mount the filesystems.
WARNING: This approach does leave you with a mirror on either box so you need to mirror them to additional drives ASAP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2003 01:09 PM
07-17-2003 01:09 PM
Re: i-node edit recovery plan
You are the GREATEST!
Thanks again!!
~jdk