public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* swalloc/allocsize question
@ 2015-08-03 17:27 Joe Landman
  2015-08-03 22:23 ` Dave Chinner
  0 siblings, 1 reply; 2+ messages in thread
From: Joe Landman @ 2015-08-03 17:27 UTC (permalink / raw)
  To: xfs

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 ?

FWIW: we are using xfs-tools 3.2.2, kernel 3.18.12.  I've also seen this 
with the 3.10 series though, so I am not sure where to look to track 
this down.  Any guidance/suggestion?  Thanks!

Joe

joe.landman@gmail.com


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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-08-03 22:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-03 17:27 swalloc/allocsize question Joe Landman
2015-08-03 22:23 ` Dave Chinner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox