From: Richard Ems <richard.ems@cape-horn-eng.com>
To: xfs@oss.sgi.com
Subject: XFS unlink still slow on 3.1.9 kernel ?
Date: Mon, 13 Feb 2012 17:57:58 +0100 [thread overview]
Message-ID: <4F394116.8080200@cape-horn-eng.com> (raw)
Hello list !
I ran a "find dir" on one directory with 11 million files and dirs in it
and it took 100 minutes. Is this a "normal" run time to be expected?
I am running openSUSE 12.1, kernel 3.1.9-1.4-default. The 20 TB XFS
partition is 100% full and is on an external InforTrend RAID system with
24 x 1 TB SATA HDDs on RAID 6 with one hot-spare HDD, so 21 data discs
plus 2 parity discs plus 1 hot-spare disc. The case is connected through
SCSI.
The system was not running anything else on that discs and the load on
the server was around 1 because of only this one find command running.
I am asking because I am seeing very long times while removing big
directory trees. I thought on kernels above 3.0 removing dirs and files
had improved a lot, but I don't see that improvement.
This is a backup system running dirvish, so most files in the dirs I am
removing are hard links. Almost all of the files do have ACLs set.
# mount | grep xfs
/dev/sda1 on /backup/IFT type xfs
(rw,noatime,nodiratime,attr2,delaylog,nobarrier,logbufs=8,logbsize=256k,sunit=256,swidth=5376,noquota,_netdev)
Any thoughts?
Thanks, Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-02-13 16:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 16:57 Richard Ems [this message]
2012-02-13 17:08 ` XFS unlink still slow on 3.1.9 kernel ? Christoph Hellwig
2012-02-13 17:11 ` Richard Ems
2012-02-13 17:15 ` Christoph Hellwig
2012-02-13 17:26 ` Richard Ems
2012-02-13 17:29 ` Christoph Hellwig
2012-02-13 17:53 ` Richard Ems
2012-02-13 18:02 ` Christoph Hellwig
2012-02-13 18:06 ` Richard Ems
2012-02-13 18:10 ` Christoph Hellwig
2012-02-13 18:18 ` Richard Ems
2012-02-13 18:48 ` Richard Ems
2012-02-13 21:16 ` Christoph Hellwig
2012-02-14 5:31 ` Stan Hoeppner
2012-02-14 9:48 ` Richard Ems
2012-02-14 19:43 ` Christoph Hellwig
2012-02-14 9:49 ` Richard Ems
2012-02-14 10:54 ` Richard Ems
2012-02-14 11:44 ` Richard Ems
2012-02-14 0:09 ` Dave Chinner
2012-02-14 12:32 ` Richard Ems
2012-02-14 19:45 ` Christoph Hellwig
2012-02-15 12:07 ` Richard Ems
2012-02-15 1:27 ` Dave Chinner
2012-02-15 12:07 ` Richard Ems
-- strict thread matches above, loose matches on Subject: below --
2012-02-14 13:02 Richard Ems
[not found] ` <4F3AA191.9030606@mnsu.edu>
2012-02-14 18:12 ` Richard Ems
2012-02-14 19:07 ` Christoph Hellwig
2012-02-15 12:48 ` Richard Ems
2012-02-14 23:10 ` Stan Hoeppner
2012-02-15 15:54 ` Richard Ems
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=4F394116.8080200@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.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.