From: Michael Weissenbacher <mw@dermichi.com>
To: xfs@oss.sgi.com
Subject: Is it possible to change sunit of log section post-mkfs
Date: Tue, 3 Nov 2015 13:18:53 +0100 [thread overview]
Message-ID: <5638A62D.1020802@dermichi.com> (raw)
Hi!
I have a XFS file system which lies on a 10-disk RAID-6 device that was
created with Chunk Size = 1MiB.
On mkfs.xfs time this was - as far as i know - specified with "-d
su=1m,sw=8".
xfs_info shows the following:
meta-data=/dev/sdb1 isize=256 agcount=15,
agsize=268435200 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=3905945088, imaxpct=5
= sunit=256 swidth=2048 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=521728, version=2
= sectsz=512 sunit=8 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Interestingly, the sunit value of the log seems to be incorrect - as it
should be 256 too, like the sunit value of the data. I am pretty sure
the reason is that the log sunit cannot be 256 blks (=1024KiB) and
because of this mkfs.xfs did fall back to the default of 8 blks
(=32KiB). I found evidence of this in the following thread:
http://oss.sgi.com/archives/xfs/2012-06/msg00431.html
What i want to achieve is to set the log sunit to the maximum possible
of 64 blks (=256KiB).
- Is that even possible without doing mkfs.xfs (and losing all data)?
- Would it be an improvement performance-wise?
- Would changing to an external log help?
tia,
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-11-03 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 12:18 Michael Weissenbacher [this message]
2015-11-03 13:02 ` Is it possible to change sunit of log section post-mkfs Brian Foster
2015-11-03 19:22 ` Michael Weissenbacher
2015-11-03 19:39 ` Brian Foster
2015-11-03 19:11 ` Dave Chinner
2015-11-03 19:32 ` Michael Weissenbacher
2015-11-03 19:48 ` Dave Chinner
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=5638A62D.1020802@dermichi.com \
--to=mw@dermichi.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.