From: "Peter Kukol" <pkukol@google.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, "Michael Rubin" <mrubin@google.com>,
"Frank Mayhar" <fmayhar@google.com>
Subject: Re: No-journal option for ext4
Date: Tue, 7 Oct 2008 07:59:17 -0700 [thread overview]
Message-ID: <929ffc5e0810070759p39310eb4m53e239e83e951079@mail.gmail.com> (raw)
In-Reply-To: <20081007054530.GI9337@mit.edu>
Thanks for the great suggestions - they all make perfect sense. I did
see the "journal present" flag, BTW, but figured that it might be
safer not to change existing behavior - e.g. when someone accidentally
says ext4 instead of ext2 when mounting an ext2 volume, right now they
get an error. If folks are OK with this changing to a successful
mount, I'm happy - less code/work is good ;-).
I'll rework my patch and send out an update when it's ready.
Thanks again!
PeterK
next prev parent reply other threads:[~2008-10-07 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 1:39 No-journal option for ext4 Peter Kukol
2008-10-07 5:45 ` Theodore Tso
2008-10-07 14:59 ` Peter Kukol [this message]
2008-10-07 15:28 ` Eric Sandeen
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=929ffc5e0810070759p39310eb4m53e239e83e951079@mail.gmail.com \
--to=pkukol@google.com \
--cc=fmayhar@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mrubin@google.com \
--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