I recently encountered some errors from my JFS file system and thought I'd consult this list for any experience on it. Should I change my JFS version or something? Rebuild my file system? Not use this version of JFS?
I built the 2.6.3 kernel.org image, probably upgraded the JFS in the kernel with a download from the IBM web page, also updated the jfs-tools package. Some issues related to my sound card led me to upgrade my kernel to 2.6.4-rc1 and for sanity's sake had me upgrading to the final 2.6.4 kernel. After the upgrade some files in /etc were found to be corrupted. I don't know when or why the corruption happened or if fsck.jfs is correct that things are now correct. Why might this have gone bad? As far as I'm aware, there isn't an hardware problem. Its all stored on a new serial ATA drive which is why I'm using the 2.6 kernel. I've included all the potential debugging information that I could dig up. I have a dd copy of the partition on which I can hack if that's something that desired. Josh Jore The transcript from jfs_logdump are available in a 280K gzipped text file at http://lik.grenekatz.org/jfs/jfslog.dmp.gz. The syslog errors: blkno = 65616b656e, nblocks = 72672e ERROR: (device hde2): dbUpdatePMap: blocks are outside the map ERROR: (device hde2): remounting filesystem as read-only blkno = 3a30383031, nblocks = 383439 ERROR: (device hde2): dbUpdatePMap: blocks are outside the map blkno = 65616b656e, nblocks = 72672e ERROR: (device hde2): dbFree: block to be freed is outside the map blkno = 3a30383031, nblocks = 383439 ERROR: (device hde2): dbFree: block to be freed is outside the map The jfs_fscklog transcript: /sbin/fsck.jfs version 1.1.3, 05-Sep-2003 processing started: 3/27/2004 14.16.32 FSCK Device /dev/hde2 is currently mounted READ ONLY. The current device is: /dev/hde2 Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 Primary superblock is valid. The type of file system for the device is JFS. Block size in bytes: 4096 Filesystem size in blocks: 512071 **Phase 0 - Replay Journal Log LOGREDO: Log already redone! logredo returned rc = 0 **Phase 1 - Check Blocks, Files/Directories, and Directory Entries **Phase 2 - Count links **Phase 3 - Duplicate Block Rescan and Directory Connectedness **Phase 4 - Report Problems **Phase 5 - Check Connectivity **Phase 6 - Perform Approved Corrections **Phase 7 - Rebuild File/Directory Allocation Maps **Phase 8 - Rebuild Disk Allocation Maps Filesystem Summary: Blocks in use for inodes: 1504 Inode count: 12032 File count: 7703 Directory count: 773 Block count: 512071 Free block count: 483610 2048284 kilobytes total disk space. 1466 kilobytes in 773 directories. 101527 kilobytes in 7703 user files. 0 kilobytes in extended attributes 0 kilobytes in access control lists 13783 kilobytes reserved for system use. 1934440 kilobytes are available for use. Filesystem is clean. All observed inconsistencies have been repaired. Filesystem has been marked clean. **** Filesystem was modified. **** processing terminated: 3/27/2004 14:16:33 with return code: 0 exit code: 0.
pgp00000.pgp
Description: PGP signature
