From: Eric Sandeen <sandeen@sandeen.net>
To: erkki.lintunen@iki.fi
Cc: xfs@oss.sgi.com
Subject: Re: an occational trouble with xfs file system which xfs_repair 2.7.14 has been able to fix
Date: Mon, 10 Mar 2008 08:31:42 -0500 [thread overview]
Message-ID: <47D5383E.50201@sandeen.net> (raw)
In-Reply-To: <47D52BE5.6010706@iki.fi>
Erkki Lintunen wrote:
...
> commands in a script. When the trouble begins cp -al command starts to
> take several hours and hundreds of megs memory. rm -fr of a subtree also
> takes considerably longer than rm a subtree in another bigger tree in
> the same filesystem, but the rm commands have always finnished, which
> the cp -al commands haven't. Most of the time the cp -al process has D
> status.
...
> What else information I could provide in addition to those requested in FAQ?
When you get a process in the D state, do echo t > /proc/sysrq-trigger
to get backtraces of all processes; or echo w to get all blocked processes.
-Eric
next prev parent reply other threads:[~2008-03-10 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 12:39 an occational trouble with xfs file system which xfs_repair 2.7.14 has been able to fix Erkki Lintunen
2008-03-10 13:31 ` Eric Sandeen [this message]
2008-03-11 18:14 ` Erkki Lintunen
2008-03-13 9:12 ` Erkki Lintunen
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=47D5383E.50201@sandeen.net \
--to=sandeen@sandeen.net \
--cc=erkki.lintunen@iki.fi \
--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.