From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <esandeen@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Andreas Dilger <adilger@dilger.ca>,
Carlos Maiolino <cmaiolino@redhat.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: new block group bitmaps not being initialized after resize!?
Date: Sun, 13 Jan 2013 08:37:06 -0500 [thread overview]
Message-ID: <20130113133706.GA30477@thunk.org> (raw)
In-Reply-To: <AA104FC2-C0C6-4465-8AA1-74D99E19EE9C@redhat.com>
On Sun, Jan 13, 2013 at 12:26:45AM -0500, Eric Sandeen wrote:
> > The flag names are confusing. INODE_ZEROED means that the inode table
> > is not zero'ed.
>
> Please tell me you said that backwards?
Yes, sorry...
> If setting the unused inode count is enough, then I guess it's resolved...
Well, modulo a patch to make sure the lazy init thread gets kicked
off, so that eventually we do end up zeroing the inode table (just in
case something goes wrong and we can't trust the block group
descriptor checksum). I just finished that off last night, and it's
now ready for review (see next message).
- Ted
next prev parent reply other threads:[~2013-01-13 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 0:07 new block group bitmaps not being initialized after resize!? Carlos Maiolino
2013-01-11 1:07 ` Eric Sandeen
2013-01-11 6:44 ` Andreas Dilger
2013-01-11 15:47 ` Eric Sandeen
2013-01-13 4:36 ` Theodore Ts'o
2013-01-13 5:26 ` Eric Sandeen
2013-01-13 13:37 ` Theodore Ts'o [this message]
2013-01-13 13:42 ` [PATCH] ext4: trigger the lazy inode table initialization after resize Theodore Ts'o
2013-01-14 13:04 ` Carlos Maiolino
2013-01-14 14:33 ` Theodore Ts'o
2013-01-14 14:42 ` Carlos Maiolino
2013-01-14 14:45 ` Carlos Maiolino
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=20130113133706.GA30477@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=cmaiolino@redhat.com \
--cc=esandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 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).