From: Karel Zak <kzak@redhat.com>
To: Roger Leigh <rleigh@codelibre.net>
Cc: util-linux@vger.kernel.org
Subject: Re: Preservation of non-kernel mount options
Date: Thu, 10 Jan 2013 11:07:45 +0100 [thread overview]
Message-ID: <20130110100745.GB19166@x2.net.home> (raw)
In-Reply-To: <20130108104443.GF3739@codelibre.net>
On Tue, Jan 08, 2013 at 10:44:43AM +0000, Roger Leigh wrote:
> Options like _netdev, comment= etc. are currently just ignored by
> mount AFAICS. It would however be quite useful if they could be
> preserved in e.g. utab if possible so that you can use this to
> label mounts so that you can query for the information later using
> e.g. mount or findmnt. Is this something which might be possible
> to add if it's not already possible?
The goal is to minimize number of situations when anything about
mountpoints is maintained in userspace. It's usually too tricky to
keep the userspace information synchronized with in-kernel
information (imagine things like namespaces, sandboxes, ...).
> It turned out (at least in Debian) that some users were using the
> "bind" option to track which filesystems were to be e.g. backed up,
> space usage checked etc. (or not). With the switch to /proc/mounts
> this information has been lost. While using the bind option to do
> this is debatable, I was looking for a better and more robust
> solution to their problem, and being able to attach comments to
> the mounts seemed like it would fit in with the existing tools
> if they could be stored.
Would be possible to improve the backup scripts to maintain
information about *filesystems* in userspace and address the
information by filesystem UUIDs? Something like
/var/log/backup-info/<UUID>/item{A,B,C}
the UUID is stable, you will not affected by things like namespaces,
umount/mount/move/... operations. The info will be completely
independent on mountpoints and found the filesystem in the findmnt(8)
or lsblk(8) output by UUID is pretty simple.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2013-01-10 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 10:44 Preservation of non-kernel mount options Roger Leigh
2013-01-10 10:07 ` Karel Zak [this message]
2013-01-21 13:16 ` Roger Leigh
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=20130110100745.GB19166@x2.net.home \
--to=kzak@redhat.com \
--cc=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