From: Roger Leigh <rleigh@codelibre.net>
To: Util-Linux <util-linux@vger.kernel.org>
Subject: A few small findmnt/mount issues
Date: Thu, 14 Mar 2013 00:21:47 +0000 [thread overview]
Message-ID: <20130314002147.GR23093@codelibre.net> (raw)
Hi,
Just noticed a few minor deficiencies:
- findmnt does not have column types for DUMP and PASS, so it's
not possible to get at all the fstab information when using the
--fstab option, unless there's a way of doing this I'm unaware
of. For completeness, it would be very useful to be able to
retrieve all fstab(5) fields. This would mean all access to
mtab and fstab can go via findmnt in our init scripts.
- utab isn't updated on remount for _netdev:
If I have an fstab entry with _netdev in the fs_mntopts, this
will get stored in utab when I run "mount /foo". However, if
I want to add the option after mount and use
"mount -o remount,_netdev /foo", this does not cause utab to
be updated.
While this might appear contrived, we do actually make use of this
when filesystems mounted in an initramfs using busybox mount are
remounted with additional options from fstab with the util-linux
mount after init starts. When we had a static mtab, the _netdev
option would have been added at this point; with utab, we would
ideally like to be able to update the option via the mount
interface. Tested this with 2.20.1, but looking at the source
looks like it's probably still present unless I misunderstood it.
May also affect other mount options?
Is there a preferred bugtracker you would like things like this
reporting, or is here OK?
Kind regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
next reply other threads:[~2013-03-14 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 0:21 Roger Leigh [this message]
2013-03-14 10:14 ` A few small findmnt/mount issues Karel Zak
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=20130314002147.GR23093@codelibre.net \
--to=rleigh@codelibre.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox