From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: why does mkfs.xfs complain here?
Date: Wed, 11 Feb 2009 07:33:43 -0600 [thread overview]
Message-ID: <4992D3B7.7060101@sandeen.net> (raw)
In-Reply-To: <200902111310.53762@zmi.at>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-11 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 12:10 why does mkfs.xfs complain here? Michael Monnerie
2009-02-11 13:33 ` Eric Sandeen [this message]
2009-02-11 14:13 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4992D3B7.7060101@sandeen.net \
--to=sandeen@sandeen.net \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.