From: Theodore Tso <tytso@mit.edu>
To: "Trenton D. Adams" <trenton.d.adams@gmail.com>
Cc: David Rees <drees76@gmail.com>,
Christian Kujau <lists@nerdbynature.de>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: EXT4-ish "fixes" in UBIFS
Date: Fri, 3 Apr 2009 02:30:59 -0400 [thread overview]
Message-ID: <20090403063059.GO9870@mit.edu> (raw)
In-Reply-To: <9b1675090904022215u612a3c06g98c3dcf3e74571a2@mail.gmail.com>
On Thu, Apr 02, 2009 at 11:15:29PM -0600, Trenton D. Adams wrote:
>
> tdamac ~ # mount -t ext3 -o data=writeback,remount,rw /dev/s/sys /
> mount: / not mounted already, or bad option
>
> Does it have to be done on initial mount?
Yes, which means you have to use the rootflags boot command-line
option.
It's a pain that we can't switch data= modes on the fly. I believe
the problematic transiations are between data=journal and
data=!journal. Transitions between data=ordered and data=writeback
should be easy to add.
- Ted
next prev parent reply other threads:[~2009-04-03 6:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 12:48 EXT4-ish "fixes" in UBIFS Artem Bityutskiy
2009-03-28 1:22 ` Kyungmin Park
2009-03-29 12:31 ` Artem Bityutskiy
2009-03-29 12:54 ` Artem Bityutskiy
2009-03-29 12:26 ` replace() system call needed (was Re: EXT4-ish "fixes" in UBIFS) Pavel Machek
2009-03-29 12:42 ` Artem Bityutskiy
2009-03-29 12:50 ` Pavel Machek
2009-03-29 13:00 ` Artem Bityutskiy
2009-03-29 13:02 ` Pavel Machek
2009-03-29 13:07 ` Artem Bityutskiy
2009-03-29 13:22 ` Andreas T.Auer
2009-03-29 13:55 ` Artem Bityutskiy
2009-03-29 13:40 ` Pavel Machek
2009-03-29 13:57 ` Artem Bityutskiy
2009-03-29 14:00 ` Pavel Machek
2009-03-30 17:19 ` Ric Wheeler
2009-03-30 22:11 ` Pavel Machek
2009-03-29 13:01 ` Andreas T.Auer
2009-03-29 13:06 ` Artem Bityutskiy
2009-03-30 15:58 ` Diego Calleja
2009-04-03 0:09 ` EXT4-ish "fixes" in UBIFS Christian Kujau
2009-04-03 0:24 ` Trenton D. Adams
2009-04-03 0:28 ` Trenton D. Adams
2009-04-03 0:38 ` Christian Kujau
2009-04-03 0:54 ` Trenton D. Adams
2009-04-03 0:54 ` Trenton D. Adams
2009-04-03 0:59 ` Trenton D. Adams
2009-04-03 1:55 ` David Rees
2009-04-03 2:05 ` Trenton D. Adams
2009-04-03 2:19 ` David Rees
2009-04-03 2:28 ` Trenton D. Adams
2009-04-03 2:58 ` David Rees
2009-04-03 3:13 ` Trenton D. Adams
2009-04-03 3:14 ` Trenton D. Adams
2009-04-03 5:02 ` Theodore Tso
2009-04-03 5:15 ` Trenton D. Adams
2009-04-03 6:30 ` Theodore Tso [this message]
2009-04-03 18:53 ` Chris Adams
2009-04-03 18:05 ` David Rees
2009-04-09 20:17 ` Pavel Machek
2009-04-03 2:26 ` Trenton D. Adams
2009-04-03 2:05 ` Theodore Tso
2009-04-03 2:45 ` Christian Kujau
2009-04-03 2:49 ` Trenton D. Adams
2009-04-03 6:53 ` Artem Bityutskiy
[not found] <cmFiD-8uc-9@gated-at.bofh.it>
[not found] ` <cmFss-ft-15@gated-at.bofh.it>
[not found] ` <cmFsu-ft-23@gated-at.bofh.it>
[not found] ` <cmGRt-2hq-7@gated-at.bofh.it>
[not found] ` <cmH1b-2K0-11@gated-at.bofh.it>
[not found] ` <cmHkz-3d3-5@gated-at.bofh.it>
[not found] ` <cmHkA-3d3-7@gated-at.bofh.it>
[not found] ` <cmHND-3Oz-5@gated-at.bofh.it>
[not found] ` <cmJPm-7hd-5@gated-at.bofh.it>
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=20090403063059.GO9870@mit.edu \
--to=tytso@mit.edu \
--cc=Artem.Bityutskiy@nokia.com \
--cc=drees76@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=trenton.d.adams@gmail.com \
/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