xfs
[Top] [All Lists]

Re: swalloc/allocsize question

To: Joe Landman <joe.landman@xxxxxxxxx>
Subject: Re: swalloc/allocsize question
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 4 Aug 2015 08:23:53 +1000
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <55BFA467.8000707@xxxxxxxxx>
References: <55BFA467.8000707@xxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Aug 03, 2015 at 01:27:03PM -0400, Joe Landman wrote:
> Hi folks:
> 
>   I've noticed some "odd" behavior while experimenting with xfs
> mounts on relatively recent kernels (3.18 series).  Basically, the
> swalloc,allocsize=x options are being modified to something
> different.  That is:
> 
> root@usn-04:~/burn-in/fio# uname -r
> 3.18.12.scalable
> 
> root@usn-04:~/burn-in/fio# mount -o
> inode64,noatime,nodiratime,swalloc,allocsize=1280k /dev/sda /data/1
> 
> root@usn-04:~/burn-in/fio# mount | grep sda
> /dev/sda on /data/1 type xfs
> (rw,noatime,nodiratime,swalloc,attr2,inode64,allocsize=256k,noquota)
> 
> This is a hardware RAID6 with a 128k chunk size and 12 elements (so
> 10 data drives, thus the 1280k allocsize for stripe width
> allocation).  Is this something specific to xfs itself, or is this
> an issue in the mount tools ?

Please provide:

        - xfs_info output from the filesystem in question
        - dmesg output of all the mount messages

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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