All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Tso <tytso@MIT.EDU>,
	"toshi.okajima\@jp.fujitsu.com" <toshi.okajima@jp.fujitsu.com>,
	"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
	"adilger\@sun.com" <adilger@sun.com>,
	"linux-ext4\@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [RFC] do you want jbd2 interface of ext3?
Date: Mon, 22 Feb 2010 21:57:18 +0300	[thread overview]
Message-ID: <87bpfhyu7l.fsf@openvz.org> (raw)
In-Reply-To: <20100222180246.GA3112@quack.suse.cz> (Jan Kara's message of "Mon, 22 Feb 2010 21:02:47 +0300")

Jan Kara <jack@suse.cz> writes:

> 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...
Stability is relative thing. I's quite depends on usecase.
For example after triggering bug on not empty orphan list on ext3_umount
i've started full orphan-list management code revision. And both
ext3/ext4 appears to be almost broken in case of errors.
But nobody seems never catch it in real life. But still
at that time i have triggered:
1) non empty orphan list on umount for both (ext3 and ext4)
2) on_disk linked list corruption  for both
3) data blocks beyond i_size 
4) bit-difference on fsck  for both
Currently i'm working on fixes. It takes week or so.
So at least i'll reduce "project_id quota" spam flow a bit.
>   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 ;).
This time i'll try to give enough test coverage.
>
> 								Honza

  reply	other threads:[~2010-02-22 18:57 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
2010-02-22 18:57             ` Dmitry Monakhov [this message]
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=87bpfhyu7l.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --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.