public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Lars Kellogg-Stedman <lars@larsshack.org>
Cc: Christoph Hellwig <hch@caldera.de>, John Jasen <jjasen1@umbc.edu>,
	linux-kernel@vger.kernel.org,
	AmNet Computers <amnet@amnet-comp.com>,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: magic device renumbering was -- Re: Linux 2.4.2ac20
Date: Fri, 16 Mar 2001 09:11:24 +0000	[thread overview]
Message-ID: <20010316091124.A1771@redhat.com> (raw)
In-Reply-To: <200103141823.TAA11310@ns.caldera.de> <Pine.LNX.4.30.0103141410360.2004-100000@flowers.house.larsshack.org>
In-Reply-To: <Pine.LNX.4.30.0103141410360.2004-100000@flowers.house.larsshack.org>; from lars@larsshack.org on Wed, Mar 14, 2001 at 02:11:57PM -0500

Hi,

On Wed, Mar 14, 2001 at 02:11:57PM -0500, Lars Kellogg-Stedman wrote:
> > Put LABEL=<label set with e2label> in you fstab in place of the device name.
> 
> Which is great, for filesystems that support labels.  Unfortunately,
> this isn't universally available -- for instance, you cannot mount
> a swap partition by label or uuid, so it is not possible to completely
> isolate yourself from the problems of disk device renumbering.

It's not convenient, but it is certainly possible: use a
single-partition raid0 logical device with raid autostart, and you get
a logical /dev/md* device which corresponds to a single partition and
which has a fixed name which is detected by the kernel at runtime and
mapped to the correct disk, wherever the disk may be.

The IBM EVMS folks are looking to generalise this sort of probing, but
for now there is at least one solution to this problem.  LVM works too
to some extent, but it currently lacks the automatic boot-time/
device-detect-time kernel probing step that the software raid code
has.

Cheers,
 Stephen

  parent reply	other threads:[~2001-03-16  9:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-13 16:41 Linux 2.4.2ac20 David Balazic
2001-03-13 19:24 ` Nathan Walp
2001-03-13 23:02   ` Tim Wright
2001-03-14  9:31   ` David Balazic
2001-03-14 15:12     ` Nathan Walp
2001-03-14 15:36       ` magic device renumbering was -- " John Jasen
2001-03-14 16:27         ` Tim Wright
2001-03-14 18:15           ` Greg KH
2001-03-15  1:53             ` Tim Wright
2001-03-15  2:08               ` Greg KH
2001-03-14 18:23         ` Christoph Hellwig
2001-03-14 18:45           ` Peter Svensson
2001-03-14 19:11           ` Lars Kellogg-Stedman
2001-03-14 19:34             ` Andreas Dilger
2001-03-14 19:44             ` Richard B. Johnson
2001-03-15 13:46               ` John Jasen
2001-03-14 20:01             ` Christoph Hellwig
2001-03-16  9:11             ` Stephen C. Tweedie [this message]
2001-03-14 19:16           ` Andreas Dilger
2001-03-14 20:08           ` John Jasen
2001-03-15  3:04         ` Stephen Degler
  -- strict thread matches above, loose matches on Subject: below --
2001-03-15 21:50 Mikael Pettersson

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=20010316091124.A1771@redhat.com \
    --to=sct@redhat.com \
    --cc=amnet@amnet-comp.com \
    --cc=hch@caldera.de \
    --cc=jjasen1@umbc.edu \
    --cc=lars@larsshack.org \
    --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