xfs
[Top] [All Lists]

Re: why does mkfs.xfs complain here?

To: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Subject: Re: why does mkfs.xfs complain here?
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 11 Feb 2009 07:33:43 -0600
Cc: xfs@xxxxxxxxxxx
In-reply-to: <200902111310.53762@xxxxxx>
References: <200902111310.53762@xxxxxx>
User-agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
Michael Monnerie wrote:
> # mkfs.xfs -f -L ws1phptmp -b size=4096 -d su=65536,sw=4,agcount=4 -i attr=2 
> -l lazy-count=1,su=65536 /dev/sdf1
> log stripe unit specified, using v2 logs
> Allocation group size (65262) is not a multiple of the stripe unit (16)
>
> Why is above error generated at all? Shouldn't mkfs.xfs handle that 
> situation and change agsize automatically? 

Well, you constrained it fairly well. But I suppose this is a bug.

> If I then do:
> 
> # mkfs.xfs -f -L ws1phptmp -b size=4096 -d su=64k,sw=4,agsize=65262b -i 
> attr=2 -l lazy-count=1,su=65536 /dev/sdf1
> log stripe unit specified, using v2 logs
> agsize rounded to 65264, swidth = 64
> meta-data=/dev/sdf1              isize=256    agcount=4, agsize=65264 blks
>          =                       sectsz=512   attr=2
> data     =                       bsize=4096   blocks=261048, imaxpct=25
>          =                       sunit=16     swidth=64 blks, unwritten=1
> naming   =version 2              bsize=4096
> log      =internal log           bsize=4096   blocks=1200, version=2
>          =                       sectsz=512   sunit=16 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> So no problem using agsize instead agcount, where agcount complained
> about group size = 65262, which I then used without problem?

and then it chose 65264 instead.

all this is a little messy in mkfs.xfs, I suppose you've found a bug....

-Eric

> mfg zmi

<Prev in Thread] Current Thread [Next in Thread>