Re: [Jfs-discussion] Disk allocation maps bug in jfs_mkfs?

[Tim N. <jfs...@ib...>]

Great, thanks!

Any chance of getting the fsck journal replay bug on large volumes fixed in 1.1.15 as well? See "Chronic logredo failed (rc=-231) errors on large 18T volumes" for details on this...

Tim

On Jun 3, 2010, at 8:00 PM, Dave Kleikamp wrote:

> This should be fixed in cvs now.  For convenience, the attached patch
> brings jfsutils-1.1.14 up to the current state of the cvs tree.  I
> haven't tested it too extensively, but it fixes this problem and a few
> others I encountered.  Unless some other problems show up, I'll probably
> create a version 1.1.15 soon.
> 
> Thanks,
> Shaggy
> 
> On Tue, 2010-05-25 at 15:41 -0700, Tim Nufire wrote:
>> Hello,
>> 
>> 
>> I think I've found a bug in jfs_mkfs.. On a newly formated
>> volume fsck.jfs reports "Incorrect number of free blocks in AG XXX
>> detected in Block Map Control Page" and "Discrepancies detected in the
>> Block Map Control Page AG free count list". Is this a know issue? Is
>> the bug in jfs_mkfs or fsck.jfs?
>> 
>> 
>> Here's an example:
>> 
>> 
>> /sbin/jfs_mkfs -q -L id-0930461  /dev/md10
>> /sbin/jfs_mkfs version 1.1.14, 06-Apr-2009
>> 
>> 
>> Format completed successfully.
>> 
>> 
>> 19027657792 kilobytes total disk space.
>> 
>> 
>> fsck.jfs -n -v /dev/md10
>> fsck.jfs version 1.1.14, 06-Apr-2009
>> processing started: 5/25/2010 15.27.45
>> The current device is:  /dev/md10
>> Open(...READONLY...) 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:  4756914448
>> **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 - Verify File/Directory Allocation Maps
>> **Phase 8 - Verify Disk Allocation Maps
>> Incorrect number of free blocks in AG 6 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 7 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 8 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 9 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 10 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 11 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 12 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 13 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 14 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 15 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 16 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 17 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 18 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 19 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 20 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 21 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 22 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 23 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 24 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 25 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 26 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 27 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 28 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 29 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 30 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 31 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 32 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 33 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 34 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 35 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 36 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 37 detected in Block Map Control
>> Page.
>> Incorrect number of free blocks in AG 38 detected in Block Map Control
>> Page.
>> Discrepancies detected in the Block Map Control Page AG free count
>> list.
>> Incorrect data detected in disk allocation control structures.
>> Filesystem Summary:
>> Blocks in use for inodes:  8
>> Inode count:  64
>> File count:  0
>> Directory count:  1
>> Block count:  4756914448
>> Free block count:  4756155203
>> 19027657792 kilobytes total disk space.
>>        0 kilobytes in 1 directories.
>>        0 kilobytes in 0 user files.
>>        0 kilobytes in extended attributes
>>        0 kilobytes in access control lists
>>  3036980 kilobytes reserved for system use.
>> 19024620812 kilobytes are available for use.
>> File system checked READ ONLY.
>> Filesystem is dirty.
>> Filesystem is dirty but is marked clean.  In its present state,
>> the results of accessing /dev/md10 (except by this utility) are
>> undefined.
>> processing terminated:  5/25/2010 15:28:05  with return code: 0  exit
>> code: 4.
>> 
>> 
>> jfs_tune -l /dev/md10
>> jfs_tune version 1.1.14, 06-Apr-2009
>> 
>> 
>> JFS filesystem superblock:
>> 
>> 
>> JFS magic number: 'JFS1'
>> JFS version: 1
>> JFS state: clean
>> JFS flags: JFS_LINUX  JFS_COMMIT  JFS_GROUPCOMMIT  JFS_INLINELOG  
>> Aggregate block size: 4096 bytes
>> Aggregate size: 38053891680 blocks
>> Physical block size: 512 bytes
>> Allocation group size: 67108864 aggregate blocks
>> Log device number: 0x0
>> Filesystem creation: Tue May 25 15:27:31 2010
>> Volume label: 'id-0930461'
>> 
>> 
>> Running fsck.jfs in read-write mode fixes this problem so I have a
>> work around...
>> 
>> 
>> fsck.jfs -f -v /dev/md10
>> fsck.jfs version 1.1.14, 06-Apr-2009
>> processing started: 5/25/2010 15.28.28
>> The current device is:  /dev/md10
>> 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:  4756914448
>> **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:  8
>> Inode count:  64
>> File count:  0
>> Directory count:  1
>> Block count:  4756914448
>> Free block count:  4756155203
>> 19027657792 kilobytes total disk space.
>>        0 kilobytes in 1 directories.
>>        0 kilobytes in 0 user files.
>>        0 kilobytes in extended attributes
>>        0 kilobytes in access control lists
>>  3036980 kilobytes reserved for system use.
>> 19024620812 kilobytes are available for use.
>> Filesystem is clean.
>> All observed inconsistencies have been repaired.
>> Filesystem has been marked clean.
>> **** Filesystem was modified. ****
>> processing terminated:  5/25/2010 15:28:58  with return code: 0  exit
>> code: 0.
>> 
>> 
>> fsck.jfs -n -v /dev/md10
>> fsck.jfs version 1.1.14, 06-Apr-2009
>> processing started: 5/25/2010 15.29.14
>> The current device is:  /dev/md10
>> Open(...READONLY...) 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:  4756914448
>> **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 - Verify File/Directory Allocation Maps
>> **Phase 8 - Verify Disk Allocation Maps
>> Filesystem Summary:
>> Blocks in use for inodes:  8
>> Inode count:  64
>> File count:  0
>> Directory count:  1
>> Block count:  4756914448
>> Free block count:  4756155203
>> 19027657792 kilobytes total disk space.
>>        0 kilobytes in 1 directories.
>>        0 kilobytes in 0 user files.
>>        0 kilobytes in extended attributes
>>        0 kilobytes in access control lists
>>  3036980 kilobytes reserved for system use.
>> 19024620812 kilobytes are available for use.
>> File system checked READ ONLY.
>> Filesystem is clean.
>> processing terminated:  5/25/2010 15:29:33  with return code: 0  exit
>> code: 0.
>> 
>> 
>> Tim
>> ------------------------------------------------------------------------------
>> 
>> _______________________________________________
>> Jfs-discussion mailing list
>> Jfs...@li...
>> https://lists.sourceforge.net/lists/listinfo/jfs-discussion
> 
> -- 
> Dave Kleikamp
> IBM Linux Technology Center
> <v1_1_14-to-2010_06_03.patch>