From: Christoph Hellwig <hch@caldera.de>
To: jjasen1@umbc.edu (John Jasen)
Cc: <linux-kernel@vger.kernel.org>, AmNet Computers <amnet@amnet-comp.com>
Subject: Re: magic device renumbering was -- Re: Linux 2.4.2ac20
Date: Wed, 14 Mar 2001 19:23:18 +0100 [thread overview]
Message-ID: <200103141823.TAA11310@ns.caldera.de> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0103141026460.532128-100000@irix2.gl.umbc.edu>
In article <Pine.SGI.4.31L.02.0103141026460.532128-100000@irix2.gl.umbc.edu> you wrote:
> The problem:
> drivers change their detection schemes; and changes in the kernel can
> change the order in which devices are assigned names.
>
> For example, the DAC960(?) drivers changed their order of
> detecting controllers, and I did _not_ have fun, given that the machine in
> question had about 40 disks to deal with, spread across two controllers.
Put LABEL=<label set with e2label> in you fstab in place of the device name.
Christoph
P.S. UUID= work, too - but I prefer a human-readable label...
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-03-14 18:25 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 [this message]
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
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=200103141823.TAA11310@ns.caldera.de \
--to=hch@caldera.de \
--cc=amnet@amnet-comp.com \
--cc=jjasen1@umbc.edu \
--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