mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dancer <dancer@zeor.simegen.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Lars Kellogg-Stedman <lars@bu.edu>,
	Nomad the Wanderer <nomad@orci.com>,
	linux-kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: Device naming???
Date: Thu, 22 Jul 1999 12:17:35 +1000	[thread overview]
Message-ID: <37967F3F.5F3CC5A1@zeor.simegen.com> (raw)
In-Reply-To: <199907212041.QAA10609@tsx-prime.MIT.EDU>

"Theodore Y. Ts'o" wrote:
> 
> The other solution for avoiding problems if a specific SCSI drive fails
> to spin up is to use entries in /etc/fstab of the following form:
> 
> LABEL=tmp              /tmp                     ext2    defaults 1 2
> UUID=3a30d6b4-08a5-11d3-91c3-e1fc5550af17  /usr ext2    defaults 1 2
> 
> The latest mount supports this, as does the very latest e2fsprogs
> release (1.15, just released this week; see the e2fsprogs page at
> http://web.mit.edu/tytso/www/linux/e2fsprogs.html).

Where's the UUID stored? On the drive? Wouldn't this cause problems with
systems involving hot-swap drives? (Ie: If a scratch drive fails (as
many have), and I go 'eek!', swap it and reboot, the drive UUID would be
different and I'd also have to edit the fstab, right?)

Just checking...for my own information.

D

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~1999-07-22  2:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.03.9907211520330.12022-100000@csa.bu.edu>
1999-07-21 20:41 ` Theodore Y. Ts'o
1999-07-22  2:17   ` Dancer [this message]

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=37967F3F.5F3CC5A1@zeor.simegen.com \
    --to=dancer@zeor.simegen.com \
    --cc=lars@bu.edu \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=nomad@orci.com \
    --cc=tytso@mit.edu \
    /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

all inboxes | Powered by JetHome®