From: Christoph Hellwig <hch@infradead.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: util-linux@vger.kernel.org
Subject: Re: Supporting human parsable journal_dev specifiers
Date: Thu, 10 Jul 2014 07:31:19 -0700 [thread overview]
Message-ID: <20140710143119.GA13753@infradead.org> (raw)
In-Reply-To: <20140710142824.GA20753@thunk.org>
On Thu, Jul 10, 2014 at 10:28:24AM -0400, Theodore Ts'o wrote:
> I have a user request that mount be able to interpret the device
> specifier for the journal_dev mount option, so that instead of having
> to type something like
>
> mount -o journal_dev=0x0803 ....
>
> they could unstead use: "journal_dev=/dev/sda3" or even
> "journal_dev=LABEL=ext_journal". I assume the right way to do this is
> a mount helper? Or is this something that you would be willing to
> accept as a patch into util-linux?
At least for the device name the best is to implement it in the kernel,
take a look at what XFS is doing for the log device. The open by dev_t
functionality currently used by extN isn't something we like to see used
anyway.
next prev parent reply other threads:[~2014-07-10 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 14:28 Supporting human parsable journal_dev specifiers Theodore Ts'o
2014-07-10 14:31 ` Christoph Hellwig [this message]
2014-07-15 11:52 ` 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=20140710143119.GA13753@infradead.org \
--to=hch@infradead.org \
--cc=tytso@mit.edu \
--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