Topic: raid -improper shutdown

[kruhm]

I had an improper shutdown on a server with a soft raid 1. The raid came up but I suspect an corrupt filesystem. How do I fsck or e2fsck on a soft 1 raid properly?

[raem]

kruhm

Try
cat /proc/mdstat
to check the staus of the array & see if it is rebuilding.

[kruhm]

The raid is fine.

I'm concerned about the filesystem.

[raem]

kruhm

This contrib may be useful
http://www.vanhees.cc/index.php?module=ContentExpress&func=display&ceid=37

or try
man fsck

[kruhm]

I searched a little harder. According to RH, you don't need to file system check (e2fsck) a ext3 filesystem, even after an unclean shutdown.

http://www.redhat.com/support/wpapers/redhat/ext3/

[CharlieBrady]

I had an improper shutdown on a server with a soft raid 1. The raid came up but I suspect an corrupt filesystem.

What makes you suspect a corrupt filesystem?

[Reinhold]

I had an improper shutdown on a server with a soft raid 1. The raid came up but I suspect an corrupt filesystem. How do I fsck or e2fsck on a soft 1 raid properly?

An improper shutdown will just force a resync of your Raidx-array the next time you boot.
Note: Raid drivers exist on a level _below_ your filesystem ...
you will have to look for yourself  (cat /proc/mdstat) if you want to know whether everything is ok there

Your 'SME' filesystem should usually be ok after a powerout since it's ext3 and auto-journaling. (Just look at what it tells you at boot time)
If you have a serious error in your filesystem you will be informed on boot... (it will boot into single user)
A little read on ext3 .

Regards
Reinhold