linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: Ted Ts'o <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Protect group inode free counting with group lock.
Date: Tue, 29 May 2012 10:18:14 +0800	[thread overview]
Message-ID: <4FC431E6.7020206@tao.ma> (raw)
In-Reply-To: <20120528222241.GD5610@thunk.org>

On 05/29/2012 06:22 AM, Ted Ts'o wrote:
> On Thu, May 17, 2012 at 10:17:34AM +0800, Tao Ma wrote:
>> oh, I see. Yes, we mkfs the system with the following configurations:
>> mke2fs -O ^resize_inode,^uninit_bg,extent,meta_bg,flex_bg,ext_attr
>> Maybe that's the reason why it has never be met by others before. ;)
> 
> I'm curious -- is there a specific reason you're disabling the group
> descriptor checksum?  Or was that just something that was picked at
> one point and you haven't changed it since?
We are just disabling the uninit_bg so as to let the block group
initialization happen in the mkfs time. I don't know why the checksum is
also disabled by ^uninit_bg.

Thanks
Tao
> 
> Thanks,
> 
> 						- Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2012-05-29  2:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  8:49 [PATCH] ext4: Protect group inode free counting with group lock Tao Ma
2012-05-16 13:43 ` Eric Sandeen
2012-05-16 14:55   ` Tao Ma
2012-05-16 15:49     ` Eric Sandeen
2012-05-17  2:17       ` Tao Ma
2012-05-17  3:14         ` Eric Sandeen
2012-05-28 22:22         ` Ted Ts'o
2012-05-29  2:18           ` Tao Ma [this message]
2012-05-29  5:57             ` Andreas Dilger
2012-05-29 12:39               ` Ted Ts'o
2012-05-29 14:28                 ` Tao Ma
2012-05-16 14:58 ` Andreas Dilger
2012-05-16 15:10   ` Tao Ma

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=4FC431E6.7020206@tao.ma \
    --to=tm@tao.ma \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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).