public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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:41:04 -0700	[thread overview]
Message-ID: <C8AEBEA0.6E43%bchang@greenplum.com> (raw)
In-Reply-To: <4C895A7D.1030208@sandeen.net>


[-- Attachment #1.1: Type: text/plain, Size: 2014 bytes --]

Thanks,
after couple runs of tpc-H , RHEL 5.4 /dev/sdd is heavily fragmented.
so back to the original problem. it always happen on /dev/sdd


[root@sdw9 data1]# xfs_db -c frag -r /dev/sdb
actual 1773, ideal 1731, fragmentation factor 2.37%

[root@sdw9 data1]# xfs_db -c frag -r /dev/sdd
actual 43384, ideal 1726, fragmentation factor 96.02%

[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_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


67 files on both /dev/sdb and /dev/sdd.


On 9/9/10 3:06 PM, "Eric Sandeen" <sandeen@sandeen.net> wrote:

On 09/09/2010 04:59 PM, Brady Chang wrote:
> thanks guys for the feedback.
> iostat shows balanced io between two filesystems.
> testing with RHEL 54, no issues there. seems to be happening on RHEL 55
> only.

There were no xfs changes between 5.4 and 5.5 that should be relevant,
only a single bugfixes for 5.5, related to fallocate error returns.

Just FWIW.

-Eric


[-- Attachment #1.2: Type: text/html, Size: 4640 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

  reply	other threads:[~2010-09-09 23:37 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 [this message]
2010-09-10  3:23     ` Stan Hoeppner
2010-09-10  4:57       ` Stan Hoeppner
2010-09-09 23:44   ` Brady Chang

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=C8AEBEA0.6E43%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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox