From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Delay in folder access
Date: Mon, 23 Jul 2012 05:28:01 -0500 [thread overview]
Message-ID: <500D2731.5050004@hardwarefreak.com> (raw)
In-Reply-To: <assp.1551ac5709.500CEF4B.8020400@amfes.com>
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.
Please post output of 'df /raid'
Likewise, 'xfs_db -c frag /dev/[device] -r'
device being that upon which the XFS resides.
> I don't see any errors in dmesg or syslog. Does this indicate a pending
> crash?
Probably not. It probably indicates a very full and fragmented filesystem.
> Also, I do have a ".fsr" folder under /raid. All the folders listed,
> which appear empty, are dated 11/1/2010. Is it safe to delete ".fsr"?
That may be related to xfs_fsr. I've never seen such a file and I use
xfs_fsr regularly. I'd wait for one of the devs to respond here before
deleting it.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-23 10:28 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 [this message]
2012-07-23 11:48 ` Dave Chinner
2012-07-23 17:44 ` Daniel L. Miller
[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=500D2731.5050004@hardwarefreak.com \
--to=stan@hardwarefreak.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