From: Chris Mason <mason@suse.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Fabien Combernous <fcombernous@eprocess.fr>,
ext3-users@redhat.com,
jfs-discussion <jfs-discussion@www-124.southbury.usf.ibm.com>,
reiserfs <reiserfs-list@namesys.com>,
linux-xfs@oss.sgi.com
Subject: Re: Re: [ext3-users] To compare Linux journalised filesystem, part II.
Date: 24 Oct 2002 13:27:31 -0400 [thread overview]
Message-ID: <1035480451.30133.192.camel@tiny> (raw)
In-Reply-To: <20021024170826.GI28822@clusterfs.com>
On Thu, 2002-10-24 at 13:08, Andreas Dilger wrote:
> On Oct 24, 2002 18:45 +0200, Fabien Combernous wrote:
> > +--------+------------------------------------------------------------------+
> > | quotas | Again "Y" is not aqual. ext3 accept quota only on data-journaled |
> > | | filesystems, but all other journaled filesystem don't have data |
> > +--------+------------------------------------------------------------------+
>
> Granted that I have never used quotas, so it is possible that I
> am incorrect. However, my understanding is that yes, you do need
> data-journaled quota files to ensure that your quota tables don't miss
> some operations after a crash. However, you can separately select
> data journaling for files in ext3 (via chattr), even if the rest of
> the filesystem is using data=ordered (the default).
data journaling on the quota files is better. Some quota updates (dqput
calling commit_dquot) are done only by clear_inode(), which should
happen outside the transaction and won't be grouped with the actual
metadata change.
-chris
next prev parent reply other threads:[~2002-10-24 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 16:45 To compare Linux journalised filesystem, part II Fabien Combernous
2002-10-24 16:52 ` Nikita Danilov
2002-10-24 16:54 ` [Jfs-discussion] " Christoph Hellwig
2002-10-24 17:08 ` [ext3-users] " Andreas Dilger
2002-10-24 17:27 ` Chris Mason [this message]
2002-10-24 17:33 ` [reiserfs-list] " Steve Lord
2002-10-25 5:48 ` Oleg Drokin
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=1035480451.30133.192.camel@tiny \
--to=mason@suse.com \
--cc=adilger@clusterfs.com \
--cc=ext3-users@redhat.com \
--cc=fcombernous@eprocess.fr \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-xfs@oss.sgi.com \
--cc=reiserfs-list@namesys.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 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.