Mufit Eribol wrote:
Ralph Angenendt wrote:
touch /forcefsck
and reboot. This will cause all filesystems to be checked with fsck
after the reboot.
I did it several times. Unfortunately, it couldn't fix the problem.
Does it say the fsck is a success or fails?
I still get the following errors and the system goes "read only" after a
couple of minutes.
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.
It seem formatting the /mnt/raid is the way to go. However, i have to
move /mnt/raid/var to /var first. / is on another hard disk and there is
space available. there are lots of programs use var lively. How can I
move /mnt/raid/var to /var.
Boot the rescue disk. Mount the partitions someplace. Dump /old_var to
/new_var. Of course, if the /old_var fs is somewhat trash, /new_var
won't be much better.
I'd be wary of hardware problems with raid controller, cables, or disks.
That "IO failure" in your logs isn't what you want to see during fs
operations.
--
Toby Bluhm
Alltech Medical Systems America, Inc.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
