From: Marcus Pereira <marcus@task.com.br>
To: linux-xfs@oss.sgi.com
Subject: mkfs.xfs error creating large agcount an raid
Date: Sat, 25 Jun 2011 16:49:26 -0300 [thread overview]
Message-ID: <4E063BC6.9000801@task.com.br> (raw)
I have an issue when creating xfs volume using large agcounts on raid
volumes.
/dev/md0 is a 4 disks raid 0 array:
----------------------------------------
# mkfs.xfs -V
mkfs.xfs version 3.1.4
# mkfs.xfs -d agcount=1872 -b size=4096 /dev/md0 -f
Warning: AG size is a multiple of stripe width. This can cause performance
problems by aligning all AGs on the same disk. To avoid this, run mkfs with
an AG size that is one stripe unit smaller, for example 147840.
log stripe unit (524288 bytes) is too large (maximum is 256KiB)
log stripe unit adjusted to 32KiB
meta-data=/dev/md0 isize=256 agcount=1872,
agsize=147968 blks
= sectsz=512 attr=2, projid32bit=0
data = bsize=4096 blocks=276810752, imaxpct=5
= sunit=128 swidth=512 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=135168, version=2
= sectsz=512 sunit=8 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
mkfs.xfs: pwrite64 failed: No space left on device
# mkfs.xfs -d agcount=1871 -b size=4096 /dev/md0 -f
Warning: AG size is a multiple of stripe width. This can cause performance
problems by aligning all AGs on the same disk. To avoid this, run mkfs with
an AG size that is one stripe unit smaller, for example 147840.
log stripe unit (524288 bytes) is too large (maximum is 256KiB)
log stripe unit adjusted to 32KiB
meta-data=/dev/md0 isize=256 agcount=1871,
agsize=147968 blks
= sectsz=512 attr=2, projid32bit=0
data = bsize=4096 blocks=276810752, imaxpct=5
= sunit=128 swidth=512 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=135168, version=2
= sectsz=512 sunit=8 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
----------------------------------------------
Any agcount greater then 1871 will lead an error, below that is OK.
I have the same issue when creating xfs volumes on a lvm stripe but with
different agcounts.
When the volume is not on an raid array any number of agcount is OK, so
seems the problem is when sunit/swidth is used.
Marcus
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-06-25 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 19:49 Marcus Pereira [this message]
2011-06-26 2:09 ` mkfs.xfs error creating large agcount an raid Stan Hoeppner
2011-06-26 5:53 ` Marcus Pereira
2011-06-26 21:26 ` Stan Hoeppner
2011-06-26 23:29 ` Stan Hoeppner
2011-06-26 23:59 ` Dave Chinner
2011-06-27 3:33 ` Stan Hoeppner
2011-06-27 4:14 ` Marcus Pereira
2011-06-27 8:55 ` Stan Hoeppner
2011-06-27 13:04 ` Paul Anderson
2011-06-27 15:10 ` Eric Sandeen
2011-06-27 15:27 ` Paul Anderson
2011-06-27 15:37 ` Eric Sandeen
2011-06-27 20:55 ` Stan Hoeppner
2011-06-28 1:22 ` 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=4E063BC6.9000801@task.com.br \
--to=marcus@task.com.br \
--cc=linux-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