public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAID superblock confusion
Date: Wed, 10 Apr 2002 13:38:12 -0600	[thread overview]
Message-ID: <20020410193812.GE3509@turbolinux.com> (raw)
In-Reply-To: <200204101533.g3AFXwS09100@vindaloo.ras.ucalgary.ca> <20020410184010.GC3509@turbolinux.com> <200204101924.g3AJOp113305@vindaloo.ras.ucalgary.ca>

On Apr 10, 2002  13:24 -0600, Richard Gooch wrote:
> Andreas Dilger writes:
> > On Apr 10, 2002  09:33 -0600, Richard Gooch wrote:
> > > Even though I'm using persistent superblockss, which is supposed to
> > > allow one to move devices from one controller to another, I can't
> > > use my RAID) set in this configuration. Looks like a bug.
> > > 
> > > md0: former device scsi/host2/bus0/target1/lun0/part2 is unavailable,
> > >      removing from array!
> > > md: md0, array needs 6 disks, has 5, aborting.
> > 
> > Note that this appears to be your real problem.
> 
> No. I tested all 6 partitions used in the RAID set. They are all
> available.

Well, MD seems to think it is unavailable...  I would check the codepath
that generates this message and see why it is happening.  Maybe it is a
timing issue or something, that MD autostart is starting before this
device is set up or something?  I don't know.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-04-10 19:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 15:33 RAID superblock confusion Richard Gooch
2002-04-10 18:40 ` Andreas Dilger
2002-04-10 19:24   ` Richard Gooch
2002-04-10 19:38     ` Andreas Dilger [this message]
2002-04-10 20:37       ` Richard Gooch
2002-04-10 21:36         ` Mike Fedyk
2002-04-10 21:39           ` Richard Gooch
2002-04-10 22:09             ` Mike Fedyk
2002-04-10 22:49               ` Richard Gooch
2002-04-10 23:36                 ` Mike Fedyk
2002-04-11 10:07                   ` Luigi Genoni
2002-04-13 19:29                     ` Richard Gooch
2002-04-13 23:55                       ` Mike Fedyk
2002-04-14  0:00                         ` Richard Gooch
2002-04-14  0:17                           ` Mike Fedyk
2002-04-11  1:38         ` Neil Brown
2002-04-11  2:41           ` Mike Fedyk
2002-04-11  6:42             ` Keith Owens
2002-04-11  8:37             ` Helge Hafting
2002-04-13 19:26           ` Richard Gooch
2002-04-18  1:54             ` Neil Brown
2002-04-18  2:10               ` Mike Fedyk
2002-04-18  2:23                 ` Neil Brown
2002-04-18  2:59                   ` Mike Fedyk
2002-04-18 14:49                   ` Richard Gooch
2002-04-19 13:42                     ` Luigi Genoni
2002-04-19 13:48                       ` Richard Gooch
2002-04-20  0:50                         ` Luigi Genoni
  -- strict thread matches above, loose matches on Subject: below --
2002-04-11  3:18 Neil Brown
2002-04-11 10:19 ` Luigi Genoni
2002-04-11 20:18   ` Mike Fedyk
2002-04-18  3:05 Neil Brown

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=20020410193812.GE3509@turbolinux.com \
    --to=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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