xfs
[Top] [All Lists]

Re: Alignment size?

To: Michael Tokarev <mjt@xxxxxxxxxx>
Subject: Re: Alignment size?
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 17 Aug 2010 10:31:16 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <4C69D554.4010407@xxxxxxxxxxxxxxxx>
References: <4C64715F.8060000@xxxxxxxxxxxxxxxx> <20100812234911.GC10429@dastard> <4C64E52E.2060806@xxxxxxxxxxxxxxxx> <20100813113915.GD10429@dastard> <4C69D554.4010407@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Tue, Aug 17, 2010 at 04:18:28AM +0400, Michael Tokarev wrote:
> 13.08.2010 15:39, Dave Chinner wrote:
> > On Fri, Aug 13, 2010 at 10:24:46AM +0400, Michael Tokarev wrote:
> []
> >> And a related question, -- is there a way to create
> >> xfs fs with the right sector size?  The filesystem
> >> were ok in years, not only on this machine, and I'm
> >> quite afraid to replace it with something else (e.g.
> >> ext4) in a hurry without good prior testing.
> > 
> > # mkfs.xfs -s <size> ....
> > 
> > if you want to set it manually. YOu shouldn't need to with any
> > relatively recent mkfs.xfs...
> 
> Um.  It appears that mkfs.xfs ignores -s size=512 on this
> raid5 array, and silently creates a filesystem with 4096
> sector size, regardless of various -s size=nn and -s log=mm
> options.
> 
> This is xfsprogs  3.1.2-1 (debian squeeze package).
> 
> So the question stands...

IIRC, the current debian xfsprogs package is still being built with
the old detection library. If you install libblkid and build
xfsprogs yourself, it should use the newer detection code and
behave as expected.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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