unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Quiliro <quiliro@riseup.net>
Cc: 27034@debbugs.gnu.org
Subject: bug#27034: mount -L will mount the first partition with the named label
Date: Tue, 23 May 2017 11:39:13 +0200	[thread overview]
Message-ID: <8737bvc3pa.fsf@elephly.net> (raw)
In-Reply-To: <20170523023853.1fd98a69@riseup.net>


Quiliro <quiliro@riseup.net> writes:

> Now that installation had failed, I decided to remove all contents of /mnt/tmp to start from 0. 
>
> lsblk recognized:
> sda as the usb installer
> sdb1 as a previous failed installation with label my-root
> sdc1 as the current installation with label my-root
>
> When I restarted to begin installation from fresh, I noticed that /mnt/etc/bare-bones.scm was changed from sda to sdc. I remember having changed it. But I started doubting. Then I checked the mount and noticed that /mnt was in sdb1 instead of in sdc1. So I umounted and mounted with -L again. But it would mount sdb1 again. So I umounted and mounted with /dev/sdc1 and no -L. That worked.

I don’t understand this bug report.  Labels must be unique.  They are
a more readable alternative to using UUIDs.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-05-23  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  1:49 bug#27034: guix system init error Quiliro
2017-05-23  1:53 ` bug#27034: (no subject) Quiliro
2017-05-23  4:35 ` bug#27034: guix system init error Leo Famulari
2017-05-23  6:03   ` Quiliro
2017-11-28 14:18     ` Ludovic Courtès
2017-05-23  7:38   ` bug#27034: mount -L will mount the first partition with the named label Quiliro
2017-05-23  9:39     ` Ricardo Wurmus [this message]
2017-05-24 18:28       ` Quiliro
     [not found]   ` <20170523023853.1fd98a69@aire>
2017-05-23  8:46     ` bug#27034: Two error have repeated consistently Quiliro
2017-05-23 10:28 ` bug#27034: (No Subject) ng0
2017-05-24 10:41 ` bug#27034: same issue here someone
2017-05-24 18:35   ` Quiliro

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737bvc3pa.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=27034@debbugs.gnu.org \
    --cc=quiliro@riseup.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).