Re: Differences in mkfs.xfs and xfs_info output.

[Jan Derfinak <ja@xxxxxxxxxxxx>]

On Wed, 20 Feb 2008, David Chinner wrote:

> On Tue, Feb 19, 2008 at 03:05:32PM +0100, Jan Derfinak wrote:
> > On Tue, 19 Feb 2008, David Chinner wrote:
> > 
> > > I did not use a patched mkfs - just my patch that does correction.
> > 
> > I tried with only your patch. The result is slightly different, but
> > not correct.
> 
> Ok, still 1024 blocks out. Still need to reproduce it locally.
> 
> FYI - thisis not a corruption bug - just an accounting problem.
> IOWs, all it will cause is slightly premature detection of ENOSPC....

Just for your information.
I tested kernel 2.6.25-rc5 compiled from sources from ftp.kernel.org.
The bug with wrong sb_fdblocks is there too:
# xfs_check /dev/system/mnt
# mount /mnt/mnt
# umount /mnt/mnt
# xfs_check /dev/system/mnt
sb_fdblocks 214009, counted 215033

# xfs_info /mnt/mnt
meta-data=/dev/mapper/system-mnt isize=256    agcount=4, agsize=554240 blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=2216960, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096  
log      =internal               bsize=4096   blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
# uname -a
Linux host 2.6.25-rc5 #1 Sun Mar 16 21:17:39 CET 2008 x86_64 x86_64 x86_64 
GNU/Linux
# xfs_repair -V
xfs_repair version 2.9.6


jan
 

--