From: Chris Sykes <chris@sigsegv.plus.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, ext2-devel@lists.sourceforge.net
Subject: Re: Hang during rm on ext2 mounted sync (2.6.14-rc2+)
Date: Fri, 23 Sep 2005 13:19:32 +0100 [thread overview]
Message-ID: <20050923121932.GA5395@sigsegv.plus.com> (raw)
In-Reply-To: <20050923015719.5eb765a4.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Fri, Sep 23, 2005 at 01:57:19AM -0700, Andrew Morton wrote:
> Odd. Seems OK here. How hard is it to make it occur?
The following always works first time on an affected kernel (I'm just
mimmicing that update-grub did at the point it hung on me):
cd /to_ext2_fs_mounted_with_sync
cp /boot/grub/menu.lst menu.lst.new
cat menu.lst.new >menu.lst
rm menu.lst.new
> I'd be suspecting a lost I/O completion from the device driver. Are you
> really sure that ext3 cannot be made to do the same thing?
I just ran the above 1000 times on 2.6.13-git10 (also affected), on
ext3, no hung rm process.
Running on ext2, rm hangs first time.
> Suggest you generate the `dmesg -s 1000000' output for both good and bad
> kernels, do a `diff -u' on them and look for IDE complaints (or SCSI, if
> you're on SCSI).
OK will do.
Initial testing suggests that 2.6.13-git9 is good while 2.6.13-git10
that I'm running now fails. I'll verify this and have a look at dmesg
output as well.
--
(o- Chris Sykes
//\ "Don't worry. Everything is getting nicely out of control ..."
V_/_ Douglas Adams - The Salmon of Doubt
GPG Fingerprint: 5E8E D17F F96C CC08 911D CAF2 9049 70D8 5143 8090
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-23 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:37 Hang during rm on ext2 mounted sync (2.6.14-rc2+) Chris Sykes
2005-09-22 20:49 ` Chris Sykes
2005-09-23 8:57 ` Andrew Morton
2005-09-23 12:19 ` Chris Sykes [this message]
2005-09-23 13:22 ` Chris Sykes
2005-09-23 19:18 ` Andrew Morton
2005-09-23 19:45 ` Jesper Juhl
2005-09-23 19:47 ` Andrew Morton
2005-09-23 20:11 ` Alexey Dobriyan
2005-09-23 20:06 ` Jesper Juhl
2005-09-23 20:23 ` Andrew Morton
2005-09-23 20:51 ` Jesper Juhl
2005-09-24 12:14 ` Chris Sykes
2005-09-24 14:28 ` Chris Sykes
2005-09-24 15:47 ` [PATCH]: Fix ext2_new_inode() failure paths Chris Sykes
2005-09-24 17:33 ` [PATCH]: Fix ext3_new_inode() " Chris Sykes
2005-09-24 17:39 ` Hang during rm on ext2 mounted sync (2.6.14-rc2+) Andrew Morton
2005-09-25 10:56 ` Chris Sykes
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=20050923121932.GA5395@sigsegv.plus.com \
--to=chris@sigsegv.plus.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--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