From: Chris Sykes <chris@sigsegv.plus.com>
To: linux-kernel@vger.kernel.org
Cc: ext2-devel@lists.sourceforge.net
Subject: Re: Hang during rm on ext2 mounted sync (2.6.14-rc2+)
Date: Thu, 22 Sep 2005 21:49:53 +0100 [thread overview]
Message-ID: <20050922204953.GA5767@sigsegv.plus.com> (raw)
In-Reply-To: <20050922163708.GF5898@sigsegv.plus.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On Thu, Sep 22, 2005 at 05:37:08PM +0100, Chris Sykes wrote:
> Ext gurus
>
> Kernels: 2.6.14-rc1 -> 2.6.14-rc2 + up to hg changeset 5c9ff0e17a61
>
> I'm experiencing processes getting stuck in the 'D' state whilst
> rm'ing files on an ext2 fs mounted with the 'sync' option. What I've
> tested so far:
>
> * Ext2 mounted with sync: rm hangs
> * Ext2 mounted without sync: OK
> * Ext3 mounted with sync: OK
> * Ext3 mounted without sync: OK
More datapoints:
2.6.13.2 is OK.
Latest 2.6.14 from the mercurial repository as of this afternoon is
still affected. I'll try to narrow it down some more with a binary
search.
It seems that not just any rm will cause the stuck process. The
following procedure seems to get it every time though (I encountered
this bug first whilst running update-grub):
# cd /sync_ext2
# cp /boot/grub/menu.lst ./menu.lst.new
# cat menu.lst.new > menu.lst
# rm menu.lst
--
(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-22 20:49 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 [this message]
2005-09-23 8:57 ` Andrew Morton
2005-09-23 12:19 ` Chris Sykes
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=20050922204953.GA5767@sigsegv.plus.com \
--to=chris@sigsegv.plus.com \
--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