linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: Doug Ledford <dledford@redhat.com>,
	Dan Williams <dan.j.williams@intel.com>,
	"Labun, Marcin" <Marcin.Labun@intel.com>,
	"Hawrylewicz Czarnowski,
	Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	linux-raid@vger.kernel.org, Bill Davidsen <davidsen@tmr.com>
Subject: Re: Auto Rebuild on hot-plug
Date: Wed, 31 Mar 2010 12:30:31 +1100	[thread overview]
Message-ID: <20100331123031.1400fd7a@notabene.brown> (raw)
In-Reply-To: <4BAB6EBD.2030503@anonymous.org.uk>

On Thu, 25 Mar 2010 14:10:05 +0000
John Robinson <john.robinson@anonymous.org.uk> wrote:


> >  Part 1.
> > 
> >   A newly hotplugged device may have metadata for RAID (0.90, 1.x, IMSM, DDF,
> >   other vendor metadata) or LVM or a filesystem.  It might have a partition
> >   table which could be subordinate to or super-ordinate to other metadata.
> >   (i.e. RAID in partitions, or partitions in RAID).  The metadata may or may
> >   not be stale.  It may or may not match - either strongly or weakly -
> >   metadata on devices in currently active arrays.
> 
> Or indeed it may have no metadata at all - it may be a fresh disc. I 
> didn't see that you stated this specifically at any point, though it was 
> there by implication, so I will: you're going to have to pick up hotplug 
> events for bare drives, which presumably means you'll also get events 
> for CD-ROM drives, USB sticks, printers with media card slots in them etc.

Correct.  We would expect that "domain path=" matching to say that those
should only be used if they already have recognisable metadata on them.
To make use of a device with no metadata already present, it would need to
appear at a path for which auto-rebuild was explicitly enabled.


> 
> >   A newly hotplugged device also has a "path" which we can see
> >   in /dev/disk/by-path.  This is somehow indicative of a physical location.
> >   This path may be the same as the path of a device which was recently
> >   removed.  It might be one of a set of paths which make up a "RAID chassis".
> >   It might be one of a set of paths one which we happen to find other RAID
> >   arrays.
> 
> Indeed, I would like to be able to declare any 
> /dev/disk/by-path/pci-0000:00:1f.2-scsi-[0-4] to be suitable candidates 
> for hot-plugging, because those are the 5 motherboard SATA ports I've 
> hooked into my hot-swap chassis.
> 
> As an aside, I just tried yanking and replugging one of my drives, on 
> CentOS 5.4, and it successfully went away and came back again, but 
> wasn't automatically re-added, even though the metadata etc was all there.

No.  That is because we have not yet implemented anything that has been
described in this document...

Thanks,
NeilBrown

  reply	other threads:[~2010-03-31  1:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  0:35 Auto Rebuild on hot-plug Neil Brown
2010-03-25  2:47 ` Michael Evans
2010-03-31  1:18   ` Neil Brown
2010-03-31  2:46     ` Michael Evans
2010-03-25  8:01 ` Luca Berra
2010-03-31  1:26   ` Neil Brown
2010-03-31  6:10     ` Luca Berra
2010-03-25 14:10 ` John Robinson
2010-03-31  1:30   ` Neil Brown [this message]
2010-03-25 15:04 ` Labun, Marcin
2010-03-27  0:37   ` Dan Williams
2010-03-29 18:10     ` Doug Ledford
2010-03-29 18:36       ` John Robinson
2010-03-29 18:57         ` Doug Ledford
2010-03-29 22:36           ` John Robinson
2010-03-29 22:41             ` Dan Williams
2010-03-29 22:46               ` John Robinson
2010-03-29 23:35             ` Doug Ledford
2010-03-30 12:10               ` John Robinson
2010-03-30 15:53                 ` Doug Ledford
2010-04-02 11:01                   ` John Robinson
2010-03-29 21:36       ` Dan Williams
2010-03-29 23:30         ` Doug Ledford
2010-03-30  0:46           ` Dan Williams
2010-03-30 15:23             ` Doug Ledford
2010-03-30 17:47               ` Labun, Marcin
2010-03-30 23:47                 ` Dan Williams
2010-03-30 23:36               ` Dan Williams
2010-03-31  4:53               ` Neil Brown
2010-03-26  6:41 ` linbloke
2010-03-31  1:35   ` Neil Brown
2010-03-26  7:52 ` Majed B.
2010-03-31  1:42   ` 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=20100331123031.1400fd7a@notabene.brown \
    --to=neilb@suse.de \
    --cc=Marcin.Labun@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=davidsen@tmr.com \
    --cc=dledford@redhat.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
    /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).