Corrupted, as in /boot disappeared once and fsck reports heaps of errors. (fsck did not successfully find /boot that time, and only found one initrd (out of 3), no kernels). i don't have any error messages at the moment (because the disk becomes read only), but i'll take a picture next time it happens. is there any way to record the fsck output to a text file if it's running from the drive itself? mount options: /dev/sda1 on / type ext4 (rw,noatime,errors=remount-ro,user_xattr,barrier=1,data=ordered,discard) tmpfs on /home/jayen/pkg/64/tmp type tmpfs (rw,nosuid,nodev,relatime,size=814512k) /dev/sda1 on /home/jayen/pkg/64/home type ext4 (rw,noatime,errors=remount-ro,user_xattr,barrier=1,data=ordered,discard) proc on /home/jayen/pkg/64/proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /home/jayen/pkg/64/dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=213489,mode=755) sysfs on /home/jayen/pkg/64/sys type sysfs (rw,nosuid,nodev,noexec,relatime) fstab: proc /proc proc defaults 0 0 UUID=2b04563a-22b9-4b8a-b7c3-98774b749d7e / ext4 errors=remount-ro,noatime,discard 0 1 /tmp /home/jayen/pkg/64/tmp bind defaults,bind 0 0 /home /home/jayen/pkg/64/home bind defaults,bind 0 0 /proc /home/jayen/pkg/64/proc bind defaults,bind 0 0 /dev /home/jayen/pkg/64/dev bind defaults,bind 0 0 /sys /home/jayen/pkg/64/sys bind defaults,bind 0 0 Thanks, Jayen On 16/08/12 15:15, Christian Kujau wrote: > On Wed, 15 Aug 2012 at 20:16, Jayen wrote: >> proc, sys, tmp, dev, and home. It all works fine, but occasionally, the >> filesystem gets corrupted (/ and /home are on the same system). I am >> running linux 3.2.21 (3.2.0-3 in debian). > > "Corrupted, as in....?" - Please post error messages, mountoptions and > fsck outputs, if attempted. > > Thanks, > Christian. > _______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
