Re: mkfs.xfs doesn't detect size of storage correctly

[Eric Sandeen <sandeen@sandeen.net>]

Matthias Schniedermeyer wrote:
> I just found a workaround. :-)
> As can be seen above the agcount is 3.
> 
> For a reason that lays years in the past, when there were issues with 
> the agcount (actually agsize), that to the best of my knowledge are 
> fixed years ago (but still cause a weird feeling whenever i see that 
> word) i just tried '-d agcount=4'
> 
> #> mkfs.xfs -l size=1024b -d agcount=4 /dev/loop6 -f
> meta-data=/dev/loop6             isize=256    agcount=4, agsize=45785912 blks
>          =                       sectsz=512   attr=2
> data     =                       bsize=4096   blocks=183143645, imaxpct=25
>          =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096
> log      =internal log           bsize=4096   blocks=32768, version=2
>          =                       sectsz=512   sunit=0 blks, lazy-count=0
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> As can be seen the "blocks"-number is much higher.
> 
> #> df -k /mnt
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/loop6           732570484      4256 732566228   1% /mnt
> 
> matches(tm) with the loop-size.
> 

Ohh.. um... Barry?  problems :)

[root@magnesium tmp]# mkfs.xfs -dfile,name=xfsfile,size=750156369920
meta-data=xfsfile                isize=256    agcount=3, agsize=45785911
blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=137357733, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096
log      =internal log           bsize=4096   blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0
[root@magnesium tmp]# bc
bc 1.06
Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
137357733*4096
562617274368

ouch... that's, um, not the right size :)

-Eric