I had a very similar problem, kernel 2.4.26.
I switched to XFS.
Terrence
Per Jessen wrote:
Hi,
I noticed that a JFS file-system on a single 300Gb IDE-drive all of a sudden was read-only, and had a closer look. After unmounting and trying to mount it again, I fscked it:
fsck -t jfs /dev/hdf1 fsck 1.26 (3-Feb-2002) fsck.jfs version 1.1.4, 30-Oct-2003 processing started: 7/9/2004 16.10.7 Using default parameter: -p The current device is: /dev/hdf1 Block size in bytes: 4096 Filesystem size in blocks: 73242335 **Phase 0 - Replay Journal Log **Phase 1 - Check Blocks, Files/Directories, and Directory Entries The root directory has an invalid data format. Will correct. **Phase 2 - Count links Incorrect link counts have been detected. Will correct. **Phase 3 - Duplicate Block Rescan and Directory Connectedness **Phase 4 - Report Problems Unable to get path for link from directory F730759 to fileset object DF730761. fsck.jfs /dev/hdf1 failed (status 0x8). Run manually!
a 2nd fsck:
fsck 1.26 (3-Feb-2002) fsck.jfs version 1.1.4, 30-Oct-2003 processing started: 7/9/2004 16.18.31 Using default parameter: -p The current device is: /dev/hdf1 Block size in bytes: 4096 Filesystem size in blocks: 73242335 **Phase 0 - Replay Journal Log **Phase 1 - Check Blocks, Files/Directories, and Directory Entries **Phase 2 - Count links Incorrect link counts have been detected. Will correct. **Phase 3 - Duplicate Block Rescan and Directory Connectedness **Phase 4 - Report Problems File system object DF730761 is linked as: 0/home/beagle-ears.com/quarantined/new cannot repair the data format error(s) in this directory. cannot repair DF730761. Will release. **Phase 5 - Check Connectivity **Phase 6 - Perform Approved Corrections 8 directories reconnected to /lost+found/. 30 files reconnected to /lost+found/. **Phase 7 - Rebuild File/Directory Allocation Maps **Phase 8 - Rebuild Disk Allocation Maps 292969340 kilobytes total disk space. 468219 kilobytes in 122207 directories. 46494998 kilobytes in 746500 user files. 0 kilobytes in extended attributes 1051513 kilobytes reserved for system use. 245891048 kilobytes are available for use. Filesystem is clean.
I had a look through /var/log/messages and found the following:
Jun 27 03:30:18 jupiter kernel: ERROR: (device ide2(33,65)): JFS:Dtree error: ino = 730761, bn=13666137, index = 0 Jun 27 03:30:18 jupiter kernel: ERROR: (device ide2(33,65)): DT_GETPAGE: dtree page corrupt Jun 27 03:30:18 jupiter kernel: ERROR: (device ide2(33,65)): JFS:Dtree error: ino = 730761, bn=13666137, index = 0 Jun 27 03:30:18 jupiter kernel: ERROR: (device ide2(33,65)): DT_GETPAGE: dtree page corrupt Jun 27 03:30:30 jupiter kernel: ERROR: (device ide2(33,65)): stack overrun in dtSearch! Jun 27 03:30:31 jupiter last message repeated 3320 times
and:
Jul 4 03:30:23 jupiter kernel: ERROR: (device ide2(33,65)): JFS:Dtree error: ino = 730761, bn=13666137, index = 0 Jul 4 03:30:23 jupiter kernel: ERROR: (device ide2(33,65)): DT_GETPAGE: dtree page corrupt Jul 4 03:30:23 jupiter kernel: ERROR: (device ide2(33,65)): JFS:Dtree error: ino = 730761, bn=13666137, index = 0 Jul 4 03:30:23 jupiter kernel: ERROR: (device ide2(33,65)): DT_GETPAGE: dtree page corrupt
This was kernel 2.4.25 and jfs-1.1.4. The drive is used purely for backup, and usually only powered up once
a day. What really happened here?
thanks, Per Jessen, Zurich
_______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
_______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
