- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Determine root cause of corrupted files on one fil...
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
06-14-2003 07:34 AM
06-14-2003 07:34 AM
Determine root cause of corrupted files on one file system
Everything went fineno issues....however, sometime between 16:00 and 08:30 the next
morning, files in the /sapmnt/XXX filesystem became corrupt:
Here's the cksum from the "new" filesystem:
# cksum /sapmnt/XXX/exe/R3trans
2197931645 5630688 /sapmnt/XXX/exe/R3trans
Here's the cksum from the old:
# cksum /sapmnt2/exe/R3trans
2580146740 5630688 /sapmnt2/exe/R3trans
Nothing in syslog, no errors on DMX frame...
Need help determining the root cause...
Of course, R3trans will not run - bu if I re-copy it - it is fine...this is not limited to just executable/binary files - have also found corrupt text files - it has only affected this 1 lvol - all others (including db's) are fine....
Thanks...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2003 09:38 AM
06-14-2003 09:38 AM
Re: Determine root cause of corrupted files on one file system
Also check lvdisplay settings on the volume since you need to have BAD BLOCK allocation set to NONE to avoid the OS from tromping on the Symmetrix.
What utility are you using to move the data?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2003 09:48 AM
06-14-2003 09:48 AM
Re: Determine root cause of corrupted files on one file system
This is the first/only host on the new DMX...
Yes, BAD BLOCK is NONE.
We just did a cp -r -p from old to new....
We maybe o to something - we were also doing an alternate restore test from Netbackup - and we may have clobbered the /sapmnt/XXX dir - even though the restore destination was /XXXtest....
The only other thing we got from HP, was, patch PHCO_27913 - we have 27408, but HP says there are some situations that may cause fil corruption if you don't have the superceded one - PHCO_29913...
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2003 11:34 AM
06-14-2003 11:34 AM
Re: Determine root cause of corrupted files on one file system
Maybe I can get this re-posted under "greatest blunders"
I was testing restore to EMC Parity RAID - and was using tar:
tar -cf - . | (cd /XXXtest; tar -xf -)
Unfortunately, I forgot the cd:
tar -cf - . | tar -xf -
I was in /sapmnt/XXX/exe dir...
DON'T TRY THAT AT HOME!
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2003 11:59 AM
06-14-2003 11:59 AM
Re: Determine root cause of corrupted files on one file system
I've gotten new cksum values when new disks and vgs are used to copy the same files from old to new file systems. I believe this is normal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2003 12:05 PM
06-14-2003 12:05 PM
Re: Determine root cause of corrupted files on one file system
Michael - cksum and the fact that you could no longer execute the files.
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2003 07:50 PM
06-14-2003 07:50 PM
Re: Determine root cause of corrupted files on one file system
Last Friday I had a bunch of filesystems go bad on a HP-UX box because while I was on vacation my backup filled up the root filesystem. Thought it was good place to stash a 500 megabyte backup. Actually it was a 800 Meg backup but only the first 576 got written before the fs filled up.
Every fs on the box vg00 got corrupt.
This was an 11.11 system L2000 64 bit.
If you had an event where root got full or near full, funny things can happen. Including the symptons you reported.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com