Hello, I recently had a system crash, and I have experienced some behavior from JFS on restart that reminds me of why I switched from reiserfs to JFS. That's not a Good Thing :-)
1. Some files contained data that no process could possibly have been writing to them. It appeared to be blocks of NULLs in some cases. Some files were .so files, and I lack the expertise to know specifically which chunks were bad, but I did know that they were corrupt (ldconfig told me). Some of the files may have contained blocks from other files also (but I'm not certain of this either). 2. Some files were truncated. This is not unexpected in a crash situation, but there were many more files like this than I would have expected. 3. The total number of files touched by #1 and #2 far exceeds the number of files open for writing at the instant the system went down. fsck didn't seem to really help. Is this behavior expected from JFS? Is there anything I can do to help out next time? I'm running a stock 2.6.6 kernel on this machine. -- John _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
