From: Alex Tomas <alex@clusterfs.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: suparna@in.ibm.com, ext2-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, alex@clusterfs.com
Subject: Re: Re: Reviewing ext3 improvement patches (delalloc, mballoc, extents)
Date: Fri, 4 Mar 2005 01:30:40 +0300 [thread overview]
Message-ID: <20050304013040.572fbabe.alex@clusterfs.com> (raw)
In-Reply-To: <20050303221010.GB6140@thunk.org>
On Thu, 3 Mar 2005 17:10:10 -0500
"Theodore Ts'o" <tytso@mit.edu> wrote:
>
> This is a bit of a pet peeve of mine, since I am still getting
> personal e-mail from people who were using Red Hat 7, and decided to
> just "try out" Fedora Core 3, only to find that any filesystems
> mounted by FC3 could no longer be mountable on their RH7 or RH8
> systems. That's why I prefer users to have to do something that
> obviously acknowledges that they are making a change to their
> filesystem's compatibility prospects --- and that's something which is
> a lot more obvious with a "tune2fs -O " command, as compared to using
> a magic mount option.
>
makes sense for me. I just like to note that mount option was choosed
for the only reason: it's simple to use during debugging.
thanks, Alex
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-03 22:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 8:33 Reviewing ext3 improvement patches (delalloc, mballoc, extents) Suparna Bhattacharya
2005-03-03 9:40 ` Andreas Dilger
2005-03-03 22:10 ` Theodore Ts'o
2005-03-03 22:30 ` Alex Tomas [this message]
2005-03-04 11:13 ` Suparna Bhattacharya
2005-03-04 12:29 ` Alex Tomas
2005-03-04 18:25 ` [Ext2-devel] " Andreas Dilger
2005-03-04 1:12 ` [Ext2-devel] " Badari Pulavarty
2005-03-04 1:46 ` Mingming Cao
2005-03-04 3:26 ` Suparna Bhattacharya
2005-03-14 8:36 ` Werner Almesberger
2005-03-14 9:04 ` Suparna Bhattacharya
2005-03-14 15:02 ` Werner Almesberger
2005-03-14 15:43 ` Alex Tomas
2005-03-14 16:37 ` [Ext2-devel] " Werner Almesberger
2005-03-14 17:13 ` Alex Tomas
2005-03-15 0:28 ` Werner Almesberger
2005-03-14 22:23 ` Bryan Henderson
2005-03-15 0:42 ` Werner Almesberger
2005-03-15 21:59 ` Bryan Henderson
2005-03-04 11:30 ` [Ext2-devel] " Alex Tomas
2005-03-04 15:02 ` Alex Tomas
2005-03-13 14:41 ` Delayed alloc for ordered-mode Suparna Bhattacharya
2005-03-13 19:32 ` Badari Pulavarty
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=20050304013040.572fbabe.alex@clusterfs.com \
--to=alex@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=suparna@in.ibm.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;
as well as URLs for NNTP newsgroup(s).