From: Jan Kara <jack@suse.cz>
To: Jamie Clark <jclark@metaparadigm.com>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23pre6aa3 - possible ext3 deadlock
Date: Thu, 27 Nov 2003 13:56:09 +0100 [thread overview]
Message-ID: <20031127125609.GD17707@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <3FC56DB2.2060704@metaparadigm.com>
Hi,
> Followup to last test with 2.4.23pre6aa3. same config as before (ext3
> /ql2300 / bonnie++) I forgot to mention that I have quotas enabled on
> the partition under test.
>
> There have been a few 2.4 / quota / ext3 deadlock-type mails on the
> list recently so I'm sot sure if this is related. I can see an atime
> update in the call trace of one of the bonnies but no dquot_ calls
> anywhere. I haven't applied Jan's patch as it came out before I could
> reliably reproduce this problem.
Yes, actually there's still a deadlock there for ext3+quotas (patch is
already written but not yet included in mainline I think) but as I've
looked through the trace it doesn't seem to be the case. About a week
ago I saw a report on deadlock of 2.4.22 with just plain ext3 without
quotas - so can you try to reproduce the problem with quotas not
compiled into the kernel (or just turning them off should be enough)?
> In the meantime I'll restart testing with noatime - which is how I'd
> usually mount such a fs anyhow.
>
> The box seems to deadlock after 3-6 days of filesystem exercise. I have
> repeated this 3 times. The last run was 6 days and and then I see all
> disk I/O has ceased. The system remains pingable and sshd connects at
> the TCP layer but nothing happens after that. The root filesystem is
> ext3 but is a completely separate device (motherboard scsi) to the
> filesystems running bonnie (external FC RAID). It seems that all
> filesystem activity ceases.
>
> I have run the alt-sysrq-t ouput through ksymoops and attached. Hope
> this is useful to someone who knows.
Thanks for report
Honza
next prev parent reply other threads:[~2003-11-27 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 2:49 2.4.23pre6aa3 scsi oops Jamie Clark
2003-11-04 10:28 ` Andrea Arcangeli
2003-11-04 11:52 ` Jamie Clark
2003-11-04 12:48 ` Andrea Arcangeli
2003-11-27 3:21 ` 2.4.23pre6aa3 - possible ext3 deadlock Jamie Clark
2003-11-27 12:56 ` Jan Kara [this message]
2003-12-06 1:05 ` 2.4.23pre6aa3 scsi oops Andrea Arcangeli
2003-12-06 1:39 ` Jamie Clark
2003-12-11 2:33 ` 2.4.23aa1 ext3 oops Jamie Clark
2003-12-16 15:15 ` Marcelo Tosatti
2003-12-16 15:55 ` Jamie Clark
2003-12-17 11:42 ` David Woodhouse
2003-12-18 6:19 ` Jamie Clark
2003-12-18 6:25 ` David Woodhouse
2003-12-18 7:33 ` Jamie Clark
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=20031127125609.GD17707@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=andrea@suse.de \
--cc=jclark@metaparadigm.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).