public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel L. Miller" <dmiller@amfes.com>
To: xfs@oss.sgi.com
Subject: Re: Delay in folder access
Date: Mon, 23 Jul 2012 10:44:12 -0700	[thread overview]
Message-ID: <assp.05517082ab.500D8D6C.8090707@amfes.com> (raw)
In-Reply-To: <500D2731.5050004@hardwarefreak.com>

On 7/23/2012 3:28 AM, Stan Hoeppner wrote:
> On 7/23/2012 1:29 AM, Daniel L. Miller wrote:
>> I have an XFS partition on simple 4-disk RAID-10 array.  The array is
>> mounted at /raid.  I have a variety of subfolders - one of which is
>> /raid/data - which in turn has a number of subfolders.
>>
>> Doing a simple "ls /raid" has no problems.  Similarly, no issues with
>> "ls /raid/data/stuff".  But ... executing "ls /raid/data" results in a
>> delay, sometimes in minutes, before it returns.
> How many files are in /raid/data, excluding subdirs?  If it's many tens
> of thousands ls will be slow, but I'd not think multiple minutes worth
> of slow.
0 files, 7 subdirs, 1 symlink

>
> Please post output of 'df /raid'
df /raid
Filesystem     1K-blocks      Used Available Use% Mounted on
/dev/md0       312516096 215009428  97506668  69% /raid


> Likewise, 'xfs_db -c frag /dev/[device] -r'
xfs_db -c frag /dev/md0 -r
actual 282381, ideal 243258, fragmentation factor 13.85%

-- 
Daniel

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

  parent reply	other threads:[~2012-07-23 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  6:29 Delay in folder access Daniel L. Miller
2012-07-23 10:28 ` Stan Hoeppner
2012-07-23 11:48   ` Dave Chinner
2012-07-23 17:44   ` Daniel L. Miller [this message]
     [not found]   ` <500D8D6C.8090707@amfes.com>
2012-07-23 17:48     ` Daniel L. Miller

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=assp.05517082ab.500D8D6C.8090707@amfes.com \
    --to=dmiller@amfes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox