From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] General weirdness - a tale of woe.
Date: Thu, 28 May 2015 09:49:50 -0400 [thread overview]
Message-ID: <20150528134949.GZ11896@ns1.bonedaddy.net> (raw)
In-Reply-To: <CAGfcS_mKZi4ODw=D+587KKJcvuutk-ojH21rT0a1Rc5SbHJn_w@mail.gmail.com>
* Rich Freeman <rich0@gentoo.org> [150528 08:45]:
> On Wed, May 27, 2015 at 8:01 PM, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
[..SNIP..]
> UUIDs are often preferable in these kinds of configurations, because
> you're less likely to run into duplicate identifiers, they don't
> change, and so on. If I mount root=UUID=foo, then my initramfs will
> try really hard to find that partition and mount it. If I mount
> root=label=foo then it will still try hard, but if for some reason I
> have more than one device with that label I could end up booting from
> the wrong one. If I mount root=/dev/sda1 then my boot may fail if I
> add a new drive, if the kernel behavior changes, if the udev behavior
> changes, and so on.
>
> I don't believe either the kernel or udev makes promises about device
> names being stable. It often works out this way, but it isn't ideal
> to depend on this.
>
> --
> Rich
It's worse than just getting the wrong filesystem mounted if the wrong
filesystem gets mounted as /tmp.
OpenRC's bootmisc will wipe the /tmp directory at boot (and likely
systemd as well, but I haven't checked.)
This means if disk device names get shifted and something other than the
proper /tmp device gets mounted as /tmp then it's "restore-from-backups"
time.
This happened to me and wiped /home (the /dev/md* devices got renumbered
once.)
So I've switched to UUID mounts so that problem doesn't happen in the
future.
It's really unpleasant if that happens.
Todd
next prev parent reply other threads:[~2015-05-28 13:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 11:59 [gentoo-user] General weirdness - a tale of woe Peter Humphrey
2015-05-27 12:31 ` Canek Peláez Valdés
2015-05-27 13:02 ` Alan McKinnon
2015-05-27 13:09 ` Canek Peláez Valdés
2015-05-27 13:21 ` Rich Freeman
2015-05-27 14:16 ` Peter Humphrey
2015-05-27 20:40 ` Mick
2015-05-28 0:01 ` Peter Humphrey
2015-05-28 12:44 ` Rich Freeman
2015-05-28 13:49 ` Todd Goodman [this message]
2015-05-28 14:36 ` Peter Humphrey
2015-05-28 17:03 ` Peter Humphrey
2015-05-28 23:51 ` Rich Freeman
2015-05-29 0:10 ` Peter Humphrey
2015-05-29 8:25 ` Neil Bothwick
2015-05-29 9:13 ` Stephan Müller
2015-05-29 9:36 ` Peter Humphrey
2015-05-29 15:19 ` Mick
2015-05-29 15:28 ` Alan Grimes
2015-05-29 15:54 ` Mick
2015-05-29 23:20 ` Peter Humphrey
2015-05-30 9:00 ` Neil Bothwick
2015-05-30 11:49 ` Mick
2015-05-30 15:43 ` Peter Humphrey
2015-05-31 0:39 ` Peter Humphrey
2015-05-31 12:18 ` Mick
2015-05-31 14:01 ` Peter Humphrey
2015-05-31 14:25 ` Mick
2015-05-30 7:53 ` Alan McKinnon
2015-05-30 9:50 ` Peter Humphrey
2015-05-29 15:36 ` Peter Humphrey
2015-05-29 16:02 ` Mick
2015-06-01 17:28 ` Peter Humphrey
2015-05-27 23:40 ` Peter Humphrey
2015-05-27 18:38 ` [gentoo-user] " James
2015-05-27 20:09 ` Neil Bothwick
2015-05-27 20:31 ` Mick
2015-05-27 21:25 ` James
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=20150528134949.GZ11896@ns1.bonedaddy.net \
--to=tsg@bonedaddy.net \
--cc=gentoo-user@lists.gentoo.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