linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Wiesner Thomas <thomas@bau-konform.at>
Cc: linux-raid@vger.kernel.org
Subject: Re: mke2fs stuck in D state while creating filesystem on md*
Date: Tue, 18 Sep 2007 13:54:54 -0400	[thread overview]
Message-ID: <46F010EE.3000202@tmr.com> (raw)
In-Reply-To: <op.txtvfnrh88izfi@barton2>

Wiesner Thomas wrote:
> Before running Linux software raid on a production system, I'm trying 
> to get the hang of it and use
> 4 loopback devices on which I play with RAID5.
>
> I've:
>     * mdadm - v2.6.3 - 20th August 2007
>     * mke2fs 1.37 (21-Mar-2005) Using EXT2FS Library version 1.37
>     * Linux hazard 2.6.22.5 #2 PREEMPT Wed Aug 29 13:06:26 CEST 2007 
> i686 GNU/Linux
>
> The HDD can transfer appriximately 40MB/s and the loopback files are 
> only 200 to 350MB.
>
> Well when I create a MD with
>     mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 
> /dev/loop0 /dev/loop1 /dev/loop2
> and try to create the filesystem on it with
>     mke2fs /dev/md0
> mke2fs gets stuck in D state. Not always but sometimes. It hangs there 
> for different amounts of time, at least a
> Minute or two. (Far longer than the filesystem creation process itself 
> takes.) Afterwards, the process continues and finishes.
> Sometimes it hangs at 6/65 blocks, sometimes earlier, sometimes later, 
> but always quite early.
>
> The interesting line of a "ps ax" looks like:
>     1609 tty2     D+     0:00 mke2fs -j /dev/md0
>
> It doesn't seem to be a real showstopper, but I think it's not a 
> normal behaviour.
> While stuck, I don't see any CPU or disk activity. Trying to kill the 
> mke2fs seems to lead to
> a completely stuck mke2fs (doesn't get out of D state) but I don't 
> know that for sure, because I did
> that only once and didn't wait very long before I rebooted.
>
> The base System is a 3.1 (Sarge) with a plain Vanilla 2.6.22.5 kernel 
> and latest mdadm.
>
> If you need additional info or I should try something, I'm willing to 
> do that, because I've some time ATM.

Has there been any progress on this? I think I saw it, or something 
similar, during some testing of recent 2.6.23-rc kernels, on mke2fs took 
about 11 min longer than all the others (~2 min) and it was not 
repeatable. I worry that process of more interest will have the same hang.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  reply	other threads:[~2007-09-18 17:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 15:46 mke2fs stuck in D state while creating filesystem on md* Wiesner Thomas
2007-09-18 17:54 ` Bill Davidsen [this message]
2007-09-19  8:20   ` Wiesner Thomas
2007-09-20  1:19     ` Mike Snitzer
2007-09-20 11:26       ` Wiesner Thomas

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=46F010EE.3000202@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=thomas@bau-konform.at \
    /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).