public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Mark Tinguely <tinguely@sgi.com>,
	xfs@oss.sgi.com
Subject: Re: [PATCH v2 1/2] xfstests: introduce 279 for SEEK_DATA/SEEK_HOLE sanity check
Date: Fri, 10 Feb 2012 11:24:26 +0800	[thread overview]
Message-ID: <4F348DEA.4060502@oracle.com> (raw)
In-Reply-To: <20120209222514.GH7479@dastard>

On 02/10/2012 06:25 AM, Dave Chinner wrote:

> On Thu, Feb 09, 2012 at 10:27:05PM +0800, Jeff Liu wrote:
>> Strange, I also tried to build XFS with 2k which shown as following:
>>
>> $ sudo mkfs.xfs -b size=2k -n size=2k -f /dev/sda7
>>
>> $ xfs_info /dev/sda7
>> meta-data=/dev/sda7              isize=256    agcount=4, agsize=1418736 blks
>>          =                       sectsz=512   attr=2
>> data     =                       bsize=2048   blocks=5674944, imaxpct=25
>                                    ^^^^^^^^^^
> 
>>          =                       sunit=0      swidth=0 blks
>> naming   =version 2              bsize=2048   ascii-ci=0
>                                    ^^^^^^^^^^
> 
>> log      =internal               bsize=2048   blocks=5120, version=2
>                                    ^^^^^^^^^^
> The block size for data, metadata, directories and the log is 2k,
> just like you asked.

Sorry, I mislead you.

Yes, the block size for data and metadata, etc are ok for me, but the
allocate unit at "struct stat.st_blksize" is 4k, It should match
data->bsize=2k IMHO.

File system magic#: 0x58465342
Allocation unit: 4096 bytes
File system supports the default behavior.

$ stat --print "%o\n" /xfs/seek_test
4096

> 
>>          =                       sectsz=512   sunit=0 blks, lazy-count=1
>> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> For the non-existent realtime device, the default is an extent size
> of 4k.  However, extent size for the real time device is separate
> from the data/log device block size - it's more like the bigalloc
> ext4 functionality in that it defines the default extent allocation
> size and alignment for the RT device.

Thanks for those patiently explaining!

Cheers,
-Jeff

> 
> Cheers,
> 
> Dave.


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-02-10  3:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 14:30 [PATCH v2 1/2] xfstests: introduce 279 for SEEK_DATA/SEEK_HOLE sanity check Jeff Liu
2012-02-08  5:42 ` Dave Chinner
2012-02-09 14:01   ` Jeff Liu
2012-02-09 14:27     ` Jeff Liu
2012-02-09 22:25       ` Dave Chinner
2012-02-10  3:24         ` Jeff Liu [this message]
2012-02-10  5:20           ` Dave Chinner
2012-02-10  5:38             ` Jeff Liu

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=4F348DEA.4060502@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=tinguely@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox