From: Brady Chang <bchang@greenplum.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: fragmentation question
Date: Thu, 9 Sep 2010 16:44:16 -0700 [thread overview]
Message-ID: <C8AEBF60.6E45%bchang@greenplum.com> (raw)
In-Reply-To: <4C88EB62.5060000@sandeen.net>
[-- Attachment #1.1: Type: text/plain, Size: 3344 bytes --]
xfs_info output after the TPC-H runs are the same.
[root@sdw9 data1]# xfs_info /dev/sdd
meta-data=/dev/sdd isize=256 agcount=32, agsize=22469715 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=719030880, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=1
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
[root@sdw9 data1]# xfs_info /dev/sdb
meta-data=/dev/sdb isize=256 agcount=32, agsize=22469715 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=719030880, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=1
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
[root@sdw9 data1]# xfs_db -c frag -r /dev/sdb
actual 1799, ideal 1748, fragmentation factor 2.83%
[root@sdw9 data1]# xfs_db -c frag -r /dev/sdd
actual 54324, ideal 1749, fragmentation factor 96.78%
On 9/9/10 7:12 AM, "Eric Sandeen" <sandeen@sandeen.net> wrote:
Brady Chang wrote:
> Hello All,
> I have an issue with fragmentation on a particular device
> thanks for any advice.
>
> -Brady
>
> I have a Dell r510 with 12 disks
> 2xraid 5 (6 disks each)
> raid group1:
> 48 GB carved out for os mounted as /
> remaining space 2.7 TB for xfs mounted as /data1
> raid group2:
> 48 GB for swap
> remaining space 2.7 TB for xfs mounted as /data2
>
> The strange thing is that /data1 never gets fragmented where as /data2
> is badly fragmented.
> I believe increase allocsize would help, but not sure how to explain why
> /data2(/dev/sdd) always gets fragmented and not /data1(/dev/sdb)
>
> It's a data warehouse application. the I/O is balanced between /data1
> and /data2:
> output of xfs_db
> [root@sdw4 data1]# xfs_db -c frag -r /dev/sdb
> actual 14353, ideal 13702, fragmentation factor 4.54%
> [root@sdw4 data1]# xfs_db -c frag -r /dev/sdd
> actual 408674, ideal 13719, fragmentation factor 96.64%
so each file has 30 extents on average (actual/ideal)
> df output
> /dev/sdb 2.7T 967G 1.8T 36% /data1
> /dev/sdd 2.7T 1.1T 1.7T 39% /data2
1.1T/408674 extents is ~3M per extent, not so good.
How many files are on each fs?
> LABEL=/data1 /data1 xfs
> allocsize=1048576,logbufs=8,noatime,nodiratime 0 0
> LABEL=/data2 /data2 xfs
> allocsize=1048576,logbufs=8,noatime,nodiratime 0 0
Everything but the first option is default, BTW.
Is xfs_info output on the 2 filesystems the same?
Otherwise Emmanuel's idea is a good one, maybe it's not
as balanced as you think it is, or maybe they have aged
differently and have different amounts of freespace
(see the freesp command in xfs_db)
> By the way, the os is RHEL 5.5 kernel 2.6.18-194.11.1.el5
Was Red Hat support not helpful?
-Eric
[-- Attachment #1.2: Type: text/html, Size: 6539 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-09-09 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 0:45 fragmentation question Brady Chang
2010-09-08 1:16 ` Brady Chang
2010-09-08 7:10 ` Emmanuel Florac
2010-09-09 14:12 ` Eric Sandeen
2010-09-09 21:59 ` Brady Chang
2010-09-09 22:06 ` Eric Sandeen
2010-09-09 23:41 ` Brady Chang
2010-09-10 3:23 ` Stan Hoeppner
2010-09-10 4:57 ` Stan Hoeppner
2010-09-09 23:44 ` Brady Chang [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=C8AEBF60.6E45%bchang@greenplum.com \
--to=bchang@greenplum.com \
--cc=sandeen@sandeen.net \
--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.