From: supersud501 <supersud501@yahoo.de>
To: Theodore Tso <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH, RFC] Add new "development flag" to the ext4 filesystem
Date: Wed, 30 Jan 2008 23:26:20 +0100 [thread overview]
Message-ID: <47A0F98C.1080304@yahoo.de> (raw)
In-Reply-To: <20080122231707.GA21968@mit.edu>
Theodore Tso wrote:
> As discussed on RFC, this flag is simply a generic "this is a
> crash/burn test filesystem" marker. If it is set, then filesystem
> code which is "in development" will be allowed to mount the
> filesystem. Filesystem code which is not considered ready for
> prime-time will check for this flag, and if it is not set, it will
> refuse to touch the filesystem.
>
> As we start rolling ext4 out to distro's like Fedora, et. al, this
> makes it less likely that a user might accidentally start using ext4
> on a production filesystem; a bad thing, since that will essentially
> make it be unfsckable until e2fsprogs catches up.
>
> - Ted
>
>
how can i set this "flag" on my filesystem? i've never set any flags
before so i just removed the code from ext4-module to mount my
filesystems, but setting the flag once would make it easier i think :)
next prev parent reply other threads:[~2008-01-30 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 23:17 [PATCH, RFC] Add new "development flag" to the ext4 filesystem Theodore Tso
2008-01-23 3:55 ` Eric Sandeen
2008-01-23 16:53 ` Theodore Tso
2008-01-23 17:04 ` Eric Sandeen
2008-01-23 17:26 ` Theodore Tso
2008-01-23 21:50 ` Andreas Dilger
2008-01-25 10:05 ` Jan Kara
2008-01-25 10:50 ` Andreas Dilger
2008-01-28 12:16 ` Jan Kara
2008-01-30 22:26 ` supersud501 [this message]
2008-01-30 22:48 ` Theodore Tso
2008-01-30 23:03 ` supersud501
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=47A0F98C.1080304@yahoo.de \
--to=supersud501@yahoo.de \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@MIT.EDU \
/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