public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: 2.6.27.7 vanilla, project quota enabled and process stuck in D state (repeatable every time)
Date: Wed, 3 Dec 2008 22:42:29 +0100	[thread overview]
Message-ID: <200812032242.29326.arekm@maven.pl> (raw)
In-Reply-To: <20081203213028.GW18236@disturbed>

On Wednesday 03 of December 2008, Dave Chinner wrote:

> > D-state lock is also happening if I drop usrquota,prjquota, reboot and
> > retry the test. I assume something was written on disk that triggers the
> > problem.
>
> Unlikely - locking doesn't generally get stuck due to on disk
> corruption. Are there any other blocked processes in the machine?
> i.e. what is the entire output of 'echo w > /proc/sysrq-trigger'?

Only this one program trace visible in sysrq-w output. No other traces - so no 
other blocked programs.

> Are there any other signs of general unwellness (e.g. a CPU running
> at 100% when it shouldn't be)?

Nothing wrong.

> FWIW, if you are seeing this on two hosts, can you try to build
> a reproducable test case using a minimal data set and a simple
> set of commands? If you can do this and supply us with a
> xfs_metadump image of the filesystem plus the commands to reproduce
> the problem we'll be able to find the problem pretty quickly....

I was able to reproduce it with:

- mount fs with usrquota,prjquota
- setup /home/users/arekm/rpm as project quota id = 10
- run program below twice

[arekm@farm rpm]$ more a.c
#include <stdio.h>
 
int main() {
        int i;
 
        i = 
rename("/home/users/arekm/tmp/aa", "/home/users/arekm/rpm/testing");
        printf("ret=%d %m\n", i);
        return 0;
}
[arekm@farm rpm]$ touch /home/users/arekm/tmp/aa
[arekm@farm rpm]$ ./a.out
ret=-1 Invalid cross-device link
[arekm@farm rpm]$ ./a.out

second run hangs with D-state. 

For clarification, rpm and tmp directories are on the same 
filesystem/partition (hda2), rpm/ dir belongs to project quota id=10, tmp 
doesn't belong to any project quota.

For the rest of your questions -  Christoph promised to look at the issue 
today, so I'll wait until tomorrow and if the issue will still be a mystery 
then I'll dig out all data you asked for.

> Cheers,
>
> Dave.

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

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

  reply	other threads:[~2008-12-03 21:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 18:49 2.6.27.7 vanilla, project quota enabled and process stuck in D state (repeatable every time) Arkadiusz Miskiewicz
2008-12-02 19:03 ` Arkadiusz Miskiewicz
2008-12-03  3:20 ` Dave Chinner
2008-12-03 13:06   ` Arkadiusz Miskiewicz
2008-12-03 13:35     ` Arkadiusz Miskiewicz
2008-12-03 21:30     ` Dave Chinner
2008-12-03 21:42       ` Arkadiusz Miskiewicz [this message]
2008-12-03 22:07         ` Christoph Hellwig
2008-12-03 22:42           ` Christoph Hellwig
2008-12-03 22:09         ` Dave Chinner
2008-12-04  8:13           ` Arkadiusz Miskiewicz
2008-12-04 12:32           ` Christoph Hellwig
2008-12-04 21:34             ` Dave Chinner

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=200812032242.29326.arekm@maven.pl \
    --to=arekm@maven.pl \
    --cc=david@fromorbit.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