About FILE SYSTEM CORRUPTION ? 1

[reneford]

I have in the error report these two errors:

684A365B 0403124805 U U SYSPFS FILE SYSTEM CORRUPTION
CD546B25 0403124805 I O SYSPFS FILE SYSTEM RECOVERY REQUIRED

It was on /tmp So I unmount /tmp and run a fsck on /tmp.

It say there was a Superblock that is marked dirty.

Is there a way to determine what cause a superblock dirty, or what cause this File System Corruption?

Any idea will be appreciate...

 

[Yalinw]

# umount myfs
# fsck –p /dev/lv02
# od –x –N 64 /dev/lv02 +0x1000
0001000 1234 0234 0000 0000 0000 4000 0000 000a 0001010 0001 8000 1000 0000 2f6c 7633 0000 6c76 0001020 3300 0000 000a 0003 0100 0000 2f28 0383 0001030 0000 0001 0000 0200 0000 2000 0000 0000 0001040

0x43218765 or 0x65872143 is correct, 0x12340234 is corrupted Magic Number
To fix the corrupted Magic Number
# dd count=1 bs=4k skip=31 seek=1 if=/dev/lv02 of=/dev/lv02
# fsck /dev/lv02 2>&1 | tee /tmp/fsck.errs

 

[reneford]

When we talk about "Corrupted Magic Number" and "Superblock dirty", are we talking about the same thing?

I made an fsck and I enter YES to correct problem.
Is this do the same thing that you are proposing to me (dd count ... + fsck ...)?

Also, I don't think the command you write (fsck /dev/lv02 2>&1 | tee /tmp/fsck.errs) will help me to find what cause the filesystem corruption, because I already run it and it doesn't tell me this information.

 

[Yalinw]

Yes, Corrupted Magic Number is in Superblock, that is same thing. When you fix the problem, you have to do "dd" , then to run fsck. I don't know what is your LV name, please instead of lv02 with your LV's name.


good luck

 

[reneford]

Ok , it works.

But How Can I determine WHAT cause this superblock corrupt?

Is there a way?

 

[Yalinw]

I'm realy glad to hear that. It is hard to say what cause the superblock corrupt. You can check the system log files to determin what cause this problem.