Re: [Jfs-discussion] fsck: attempt to access beyond end of device
Brought to you by:
blaschke-oss,
shaggyk
|
From: Jeff M. <mar...@au...> - 2001-10-29 16:05:16
|
Anthony, This is a partition table problem in the kernel. The problem was introduced in 2.4.11 and should have been fixed in 2.4.13. Jeff Martin IBM (LTC-Test) Anthony Liu wrote: > Hi, > > This is a very strange problem, anyone seen something like this > in your logs? > > Doing mkfs.jfs or fsck the following will show up (11 times) > > kernel: attempt to access beyond end of device > kernel: 03:01: rw=0, want=1052228, limit=1052226 > > fdisk -l output: > > Disk /dev/had: 255 heads, 63 sectors, 5005 cylinders > Units = cylinders of 16065 * 512 bytes > > Device Boot Start End Blocks Id System > /dev/hda1 * 1 131 1052226 83 Linux > /dev/hda2 * 132 135 32130 83 Linux > /dev/hda3 136 184 393592+ 82 Linux swap > /dev/hda4 185 5005 38724682+ 5 Extended > /dev/hda5 185 3985 30531532 83 Linux > /dev/hda6 3986 4507 4192964+ 83 Linux > /dev/hda7 4508 5005 4000184+ 83 Linux > > Note: > /dev/hda6 is jfs formatted. jfsprogs 1.0.8 > Kernels tested are 2.4.13 and 2.4.13-pre3 > This problem also show up on another system/drive. > > When reboot to the same kernel, the problem disappeared... > > mkfs.jfs /dev/hda1 gives: > --cut------------------------------------------------------- > mkfs.jfs version 1.0.8, 17-Oct-2001 > > Warning! All data on device /dev/hda1 will be lost! > > Continue? (Y/N) y > - > > Format completed successfully. > > 1052226 kilobytes total disk space. > --cut------------------------------------------------------ > > However, fsck report that only 1052224k is the total: > > fsck.jfs -v -f /dev/hda1 > --cut------------------------------------------------------ > fsck.jfs version 1.0.8, 17-Oct-2001 > The current device is: /dev/hda1 > (chklog) FSCK Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 > > (chklog) FSCK Primary superblock is valid. > > (chklog) FSCK The type of file system for the device is JFS. > > Block size in bytes: 4096 > File system size in blocks: 263056 > Phase 0 - Replay Journal Log > (chklog) FSCK:LOGREDO: Journal log is now open. (major = 0x00, minor = 0x00) > > (chklog) FSCK:LOGREDO: Log already redone! > > (chklog) FSCK logredo returned rc = 0 > > Phase 1 - Check Blocks, Files/Directories, and Directory Entries. > Phase 2 - Count Links. > Phase 3 - Rescan for Duplicate Blocks and Verify Directory Tree. > 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. > (chklog) FSCK Filesystem Summary: > > (chklog) FSCK Blocks in use for inodes: 8 > > (chklog) FSCK Inode count: 64 > > (chklog) FSCK File count: 0 > > (chklog) FSCK Directory count: 1 > > (chklog) FSCK Block count: 263056 > > (chklog) FSCK Free block count: 261652 > > (chklog) 1052224 kilobytes total disk space. > > (chklog) 0 kilobytes in 1 directories. > > (chklog) 0 kilobytes in 0 user files. > > (chklog) 0 kilobytes in extended attributes > > (chklog) 0 kilobytes in access control lists > > (chklog) 5616 kilobytes reserved for system use. > > (chklog) 1046608 kilobytes are available for use. > > File system is clean. > (chklog) FSCK All observed inconsistencies have been repaired. > > (chklog) FSCK Filesystem has been marked clean. > > (chklog) FSCK **** Filesystem was modified. **** > > (chklog) FSCK processing terminated: 10/29/2001 17.35.0 with return code: 0. > > |........ > --cut------------------------------------------------------ > > After mounting /dev/hda1, copying some files to it, umount it and perform > a fsck.jfs, the same "attempt to access beyond end of device" error will > show up. The pair of messages repeated exactly 11 times when it > was triggered. > > _______________________________________________ > Jfs-discussion mailing list > Jfs...@ww... > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion |