Kai Schaetzl wrote:
Mufit Eribol wrote on Thu, 31 Jul 2008 10:08:48 +0300:
But, file system of "this volume" once in a while goes "read only" mode.
there will be log entries about this. Do a *forced* fsck.
Kai
Kai, thank you very much for the hint.
I am not sure which other log file has entries about this problem but here is the relevant section of dmesg:
md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. device-mapper: multipath: version 1.0.5 loaded EXT3 FS on md2, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on md1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs warning (device dm-0): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure EXT3-fs warning (device dm-0): ext3_clear_journal_err: Marking fs in need of filesystem check. EXT3-fs warning: mounting fs with errors, running e2fsck is recommended EXT3 FS on dm-0, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Adding 6144852k swap on /dev/sda3. Priority:1 extents:1 across:6144852k Adding 6144852k swap on /dev/sdb3. Priority:1 extents:1 across:6144852k
What is the best way to run fsck on a production system?
Thank you Mufit