Hello, 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 proven very stable. I did a kernel update to 2.6.22 in order to support ecryptfs. Unfortunately, XFS isn't supported by ecryptfs, the later claims to have been tested on EXT3 and JFS. So I reformated my array to JFS. Before implementing any ecryptfs mounts, I decided to test JFS for 2 months and see how it handles my server load or if it's stable (it can't be worse than EXT3).
Twelve days ago, the filesystem remounted itself in read-only mode. I didn't even know that would happen in case of a problem. I did a fsck in read-only mode and remounted read-write. Here is the output written in dmesg from that event : [189028.668269] ERROR: (device md0): diUpdatePMap: inode 4122 not marked as allocated in wmap! [189028.679102] ERROR: (device md0): diFree: wmap shows inode already free 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. This time dmesg tells : [974746.368996] ERROR: (device md0): diAllocIno: free inode not found in summary map Again, fsck then remount get my array back online, but this is annoying. Anyone know why this corruption would occur ? Known bug in 2.6.22 ? Before doing a fsck, I did a sanity check of the mdadm array and it was clean : therefore corruption is software. Thank you, Charles Perreault ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
