All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Joe Landman <joe.landman@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: swalloc/allocsize question
Date: Tue, 4 Aug 2015 08:23:53 +1000	[thread overview]
Message-ID: <20150803222353.GU3902@dastard> (raw)
In-Reply-To: <55BFA467.8000707@gmail.com>

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@fromorbit.com

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

      reply	other threads:[~2015-08-03 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 17:27 swalloc/allocsize question Joe Landman
2015-08-03 22:23 ` Dave Chinner [this message]

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=20150803222353.GU3902@dastard \
    --to=david@fromorbit.com \
    --cc=joe.landman@gmail.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 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.