On Tue, October 16, 2007 00:27, Charles Perreault wrote: > I've got a Ubuntu backup server using JFS on a mdadm raid 1 array. The > server has been using XFS for months on a 2.6.17 kernel and has been
You are aware of http://oss.sgi.com/projects/xfs/faq.html#dir2 ? > Twelve days ago, the filesystem remounted itself in read-only mode. I > didn't even know that would happen in case of a problem. See mount(8): Mount options for jfs [...] errors=continue / errors=remount-ro / errors=panic > I did a fsck in read-only mode and remounted read-write. Did you mean, you remounted the device RO and did fsck, or did you unmount the device and performed a RO-fsck (jfs.fsck -n). Please try to use a current version of jfsprogs and try to fsck (without -n) the device. > This morning, I woke up to find my server again remounted in read-only > mode. A funny thing is that mount reports the drive to be mounted (rw), > but it's impossible to touch any file. Sometimes /etc/mtab does not represent the contents of /proc/mounts. > Again, fsck then remount get my array back online, but this is > annoying. Anyone know why this corruption would occur ? Hm, occasional corruptions can stem from software bugs to anything like bad hardware. 2.6.23.1 is out, you could check the changelog if there's anything related to this one. But I'm more curious about the outcome of fsck on the unmounted device.... Christian. -- BOFH excuse #442: Trojan horse ran out of hay ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jfs-discussion mailing list Jfs-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jfs-discussion
