HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- file system damage
Operating System - HP-UX
1832396
Members
3259
Online
110041
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
12-17-2003 10:18 PM
12-17-2003 10:18 PM
Hello Admins,
i have to deal with a damaged file-system on a 10.20-box.
It resides on a raid-system , all the other file systems of the raid seem ok.
> fsck -F vxfs -o full /dev/rs2/rs35
log replay in progress
vxfs fsck: file system does not contain a valid log
vxfs fsck: cannot perform log replay
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = -1946760533, off = 0, len = 8192
It seems that the directory-mapping has crashed:
> vxdump -f - /dev/rs2/rs35 | vxrestore -r -f -
vxdump: Date of this level 0 dump: Thu Dec 18 12:04:47 2003
vxdump: Date of last level 0 dump: the epoch
vxdump: Dumping /dev/rs2/rrs35 (/rs2/rs35) to standard output
vxdump: mapping (Pass I) [regular files]
vxdump: mapping (Pass II) [directories]
vxdump: estimated 48333826 blocks (23600.50MB).
vxdump: dumping (Pass III) [directories]
vxdump: inode bmap failure inode 49720 offset 0
vxdump: inode bmap failure inode 49727 offset 0
vxdump: Broken pipe
vxdump: The ENTIRE dump is aborted.
Still i can get the inodes of the files i am missing ( using ff )
and according to fsdb the data seem to be all right.
Does anyone know how to extract the data by given inode-
number from that filesystem?
Thank you in advance
Martin
i have to deal with a damaged file-system on a 10.20-box.
It resides on a raid-system , all the other file systems of the raid seem ok.
> fsck -F vxfs -o full /dev/rs2/rs35
log replay in progress
vxfs fsck: file system does not contain a valid log
vxfs fsck: cannot perform log replay
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = -1946760533, off = 0, len = 8192
It seems that the directory-mapping has crashed:
> vxdump -f - /dev/rs2/rs35 | vxrestore -r -f -
vxdump: Date of this level 0 dump: Thu Dec 18 12:04:47 2003
vxdump: Date of last level 0 dump: the epoch
vxdump: Dumping /dev/rs2/rrs35 (/rs2/rs35) to standard output
vxdump: mapping (Pass I) [regular files]
vxdump: mapping (Pass II) [directories]
vxdump: estimated 48333826 blocks (23600.50MB).
vxdump: dumping (Pass III) [directories]
vxdump: inode bmap failure inode 49720 offset 0
vxdump: inode bmap failure inode 49727 offset 0
vxdump: Broken pipe
vxdump: The ENTIRE dump is aborted.
Still i can get the inodes of the files i am missing ( using ff )
and according to fsdb the data seem to be all right.
Does anyone know how to extract the data by given inode-
number from that filesystem?
Thank you in advance
Martin
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2003 11:04 PM
12-17-2003 11:04 PM
Solution
Hi Martin,
This is not an easy procedure, especially if there are indirect blocks. However, I have attached a document showing a way to do it.....you need to use fsdb to find the block mapping then use dd to copy those blocks out to a regular file. I hope it helps, any questions let me know.
Cheers,
James.
This is not an easy procedure, especially if there are indirect blocks. However, I have attached a document showing a way to do it.....you need to use fsdb to find the block mapping then use dd to copy those blocks out to a regular file. I hope it helps, any questions let me know.
Cheers,
James.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2003 12:54 AM
12-18-2003 12:54 AM
Re: file system damage
Hello James,
thanks a lot, it worked well; I was able to pick some files from the disk which i already got from a backup, but
switching to some of the newer data, the filesystem seems to
be to badly damaged. All i can get is
> 50135 i
read failed at block 3918453 error = 6
but again, thanks for your answer
Martin
thanks a lot, it worked well; I was able to pick some files from the disk which i already got from a backup, but
switching to some of the newer data, the filesystem seems to
be to badly damaged. All i can get is
> 50135 i
read failed at block 3918453 error = 6
but again, thanks for your answer
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2004 03:04 PM
03-22-2004 03:04 PM
Re: file system damage
Hello James,
Thanks a lot!
The trick to extract the files from an unmounted(or damaged) filesystem is excellent.
This shows your high level of expertise in the field of HP-UX.
Thanks & Regards,
Ismail.
Thanks a lot!
The trick to extract the files from an unmounted(or damaged) filesystem is excellent.
This shows your high level of expertise in the field of HP-UX.
Thanks & Regards,
Ismail.
No problem can stand the assault of sustained thinking.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP