From: Jan Kara <jack@suse.cz>
To: Theodore Tso <tytso@MIT.EDU>
Cc: toshi.okajima@jp.fujitsu.com, Jan Kara <jack@suse.cz>,
akpm@linux-foundation.org, adilger@sun.com,
linux-ext4@vger.kernel.org
Subject: Re: [RFC] do you want jbd2 interface of ext3?
Date: Mon, 22 Feb 2010 19:02:47 +0100 [thread overview]
Message-ID: <20100222180246.GA3112@quack.suse.cz> (raw)
In-Reply-To: <9B774728-3508-4850-B036-CB0013403DE9@mit.edu>
On Mon 22-02-10 08:55:53, Theodore Tso wrote:
> As for quota --- quite seriously --- if you have mission critical users,
> I'd suggest that they not use quota. Dimitry has been turning up all
> sorts of bugs in the quota subsystem, many of which are just as
> applicable to ext3. The real issue is that quota hasn't received as much
> testing as other file system features --- in any file system, not just
> ext4.
I don't agree with this. I know about quite a few large customers
depending on quotas on their servers and they run on ext3 / reiserfs quite
happily. Dmitry's patches touching the generic code were mostly cleanups,
the fixes were just in the delayed allocation handling but that never
gets executed for ext3 or reiserfs...
I don't say there cannot be bugs and certainly quota code has less
exposure than other more used filesystem parts. But I don't know about
any serious quota issue on ext3 / reiserfs in last two years or so
(except the one that was caused by Dmitry's fixes ;).
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-02-22 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 7:41 [RFC] do you want jbd2 interface of ext3? Toshiyuki Okajima
2010-02-16 14:31 ` tytso
2010-02-16 18:54 ` Jan Kara
2010-02-17 8:36 ` Toshiyuki Okajima
2010-02-17 16:49 ` tytso
2010-02-17 18:09 ` Greg Freemyer
2010-02-17 19:16 ` tytso
2010-02-22 5:44 ` Toshiyuki Okajima
2010-02-22 13:55 ` Theodore Tso
2010-02-22 18:02 ` Jan Kara [this message]
2010-02-22 18:57 ` Dmitry Monakhov
2010-02-26 7:25 ` Toshiyuki Okajima
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=20100222180246.GA3112@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=toshi.okajima@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.