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: Thu, 31 Jan 2008 00:03:03 +0100 [thread overview]
Message-ID: <47A10227.8080005@yahoo.de> (raw)
In-Reply-To: <20080130224820.GA20529@mit.edu>
Theodore Tso wrote:
>
> You can manually set the flag using debugfs:
>
> # debugfs -w /dev/hdXX
> debugfs: set_super_value s_flags 4
> debugfs: quit
>
> (Or, if you're lazy, you can also type the shorthand "ssv flags 4" to
> debugfs.)
>
> With e2fsprogs 1.40.5, if the test_fs flag is set, then blkid will
> return a filesystem type ext4dev, such that if your mount is
> configured to use blkid (instead of vol_id), it will automatically use
> ext4dev to mount a filesystem that has (a) a journal (since ext4
> currently requires a journal), and (b) the test_fs flag set.
>
> This makes it easier for people who are testing ext4, since they will
> just be able to do something like:
>
> # mke2fs -j -E test_fs /dev/mapper/lvmset-test
> # mount /dev/mapper/lvmset-test
>
> .. and /dev/mapper/lvmset-test will automatically be mounted using
> ext4.
>
> - Ted
thanks for your quick answer! i think i've learned something more about
ext4 and those flags.
prev parent reply other threads:[~2008-01-31 1: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
2008-01-30 22:48 ` Theodore Tso
2008-01-30 23:03 ` supersud501 [this message]
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=47A10227.8080005@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