public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Rees <dbr@greenhydrant.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Andrew Morton <akpm@zip.com.au>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	ext3-users@redhat.com
Subject: Re: kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?)
Date: Wed, 29 Aug 2001 17:55:41 -0700	[thread overview]
Message-ID: <20010829175541.E21590@greenhydrant.com> (raw)
In-Reply-To: <3B8D54F3.46DC2ABB@zip.com.au> <20010829141451.A20968@greenhydrant.com> <3B8D60CF.A1400171@zip.com.au> <20010829144016.C20968@greenhydrant.com> <3B8D6BF9.BFFC4505@zip.com.au> <20010829153818.B21590@greenhydrant.com> <3B8D712C.1441BC5A@zip.com.au> <20010829155633.D21590@greenhydrant.com> <15245.35636.82680.966567@notabene.cse.unsw.edu.au>
In-Reply-To: <15245.35636.82680.966567@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Thu, Aug 30, 2001 at 10:39:16AM +1000

On Thu, Aug 30, 2001 at 10:39:16AM +1000, Neil Brown wrote:
> 
> Thanks David and Andrew for providing all the helpful details.
> I know what happened.  As Andrew said, the raid1 buffers have simply
> disappeared into thin air.
> The line that makes them invisible is
> 			r1_bh->state = 0;
> at line 165 in drivers/md/raid1.c.  This should be more like
> 			r1_bh->state = (1 << R1BH_PreAlloc);
> We need to clear the Uptodate bit and the Phase bit, but not
> the prealloc bit.  
> 
> Linus:  Please consider applying this patch.
> 
> NeilBrown
> 
> --- drivers/md/raid1.c	2001/08/30 00:36:54	1.1
> +++ drivers/md/raid1.c	2001/08/30 00:37:03
> @@ -162,7 +162,7 @@
>  			conf->freer1 = r1_bh->next_r1;
>  			conf->freer1_cnt--;
>  			r1_bh->next_r1 = NULL;
> -			r1_bh->state = 0;
> +			r1_bh->state = (1 << R1BH_PreAlloc);
>  			r1_bh->bh_req.b_state = 0;
>  		}
>  		md_spin_unlock_irq(&conf->device_lock);

Since rebooting, I haven't encountered any problems (but I did lose a lot of
data on that partition!).  I'll apply this patch and let you know if
anything strange happens.  Otherwise assume that it works for me.

I'm curious, why hasn't this bug shown up before?  Did I just get unlucky? 
Or is everyone else using software raid1 without problems lucky?  8)

-Dave

  reply	other threads:[~2001-08-30  0:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29 20:17 kupdated, bdflush and kjournald stuck in D state on RAID1 device (deadlock?) David Rees
2001-08-29 20:47 ` Andrew Morton
2001-08-29 21:14   ` David Rees
2001-08-29 21:38     ` Andrew Morton
2001-08-29 21:40       ` David Rees
2001-08-29 22:26         ` Andrew Morton
2001-08-29 22:38           ` David Rees
2001-08-29 22:48             ` Andrew Morton
2001-08-29 22:56               ` David Rees
2001-08-30  0:39                 ` Neil Brown
2001-08-30  0:55                   ` David Rees [this message]
2001-08-30  1:17                     ` Neil Brown
2001-08-30  1:24                       ` David Rees
2001-08-30  2:05                         ` Neil Brown
2001-08-30  2:50                           ` David Rees

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=20010829175541.E21590@greenhydrant.com \
    --to=dbr@greenhydrant.com \
    --cc=akpm@zip.com.au \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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