All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Matt Burgess <matthew@linuxfromscratch.org>
Cc: util-linux@vger.kernel.org
Subject: Re: Discrepancies between real and symlinked mtab
Date: Wed, 31 Oct 2012 13:24:53 +0100	[thread overview]
Message-ID: <20121031122453.GB27908@x2> (raw)
In-Reply-To: <1351638239.1651.13.camel@kyoto.localdomain>

On Tue, Oct 30, 2012 at 11:03:59PM +0000, Matt Burgess wrote:
> 1) mount(8)
> 
> /dev/root on / type ext3 (rw,relatime,data=ordered)

 I see (Fedora 17, util-linux 2.21.2)

   /dev/sda4 on / type ext4 (rw,relatime,data=ordered)

anyway, it's not mount(8) responsibility what you have in /proc/mounts
or /proc/self/mountinfo.

> Nope, that's not /dev/sda3.  And what is /dev/root anyway? There's no
> such node under /dev here.

if I good remember there was symlink in some distributions

> 3) lsblk(8)
> 
> NAME FSTYPE LABEL UUID                                 MOUNTPOINT
> sda3 ext3   /lfs  aaf09e8b-d50e-429e-ba8e-11fa07ab5b75 

I see:

 $ lsblk --fs /dev/sda4
 NAME FSTYPE LABEL UUID                                 MOUNTPOINT
 sda4 ext4         33230ae2-1093-4353-824c-f7ca09a2a882 /

> As all 3 utils show the same issue, I assume this is something to do
> with libblkid?

We use libmount to get information about mountpoints. The libblkid is
responsible for information about filesystems (LABEL, UUID, ...).


    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  parent reply	other threads:[~2012-10-31 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 23:03 Discrepancies between real and symlinked mtab Matt Burgess
2012-10-31  7:59 ` Bernhard Voelker
2012-10-31 12:24 ` Karel Zak [this message]
2012-10-31 12:46   ` Kay Sievers
2012-10-31 14:33     ` Karel Zak
2012-11-08 13:48 ` Karel Zak
2012-11-08 13:54   ` Matthew Burgess

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=20121031122453.GB27908@x2 \
    --to=kzak@redhat.com \
    --cc=matthew@linuxfromscratch.org \
    --cc=util-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.