From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: RFC: guard against more "dangerous" userspace options
Date: Tue, 11 Aug 2009 15:43:24 -0500 [thread overview]
Message-ID: <4A81D7EC.2060706@redhat.com> (raw)
I'll keep it short and sweet:
Can we add a consistent "--eatmydata" type of hurdle to jump over before
people are allowed to use either the so-far-less-tested tools and/or
options therein?
I'm thinking of, so far:
e4defrag
mkfs.ext4 -O meta_bg (?)
mkfs.ext4 -E lazy_itable_init=1
tune2fs -I <bigger>
without the --eatmydata option (feel free to edit for clarity) we could
get something like:
"The ____ option is experimental and/or incomplete, and should be used
only for testing at this point. Please re-issue your command with
'--eatmydata' option to use this option."
Thoughts?
I'm nervous about ext4 coming into wider use and people finding some of
the bits which aren't -quite- ready for prime time yet, and winding up
with a disaster.
Thanks,
-Eric
next reply other threads:[~2009-08-11 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 20:43 Eric Sandeen [this message]
2009-08-20 6:27 ` RFC: guard against more "dangerous" userspace options Aneesh Kumar K.V
2009-08-20 14:48 ` Eric Sandeen
2009-08-21 7:02 ` Aneesh Kumar K.V
2009-08-21 14:40 ` Eric Sandeen
2009-08-21 16:08 ` Andreas Dilger
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=4A81D7EC.2060706@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@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.