From: Eric Sandeen <sandeen@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Dmitry Monakhov <dmonakhov@openvz.org>
Subject: Re: quota reservation fixes for -stable?
Date: Thu, 01 Apr 2010 08:57:52 -0500 [thread overview]
Message-ID: <4BB4A660.6030609@redhat.com> (raw)
In-Reply-To: <20100401082334.GD3322@quack.suse.cz>
Jan Kara wrote:
> On Wed 31-03-10 10:36:12, Eric Sandeen wrote:
>> I think we should get the following commits to -stable:
>>
>> 0a5a9c725512461d19397490f3adf29931dca1f2 quota: Fix warning when a delayed write happens before quota is enabled
>> c469070aea5a0ada45a836937c776fd3083dae2b quota: manage reserved space when quota is not active [v2]
> They are already queued for 2.6.33 and 2.6.32 stable trees. I sent
> them to Greg last week or so.
Oh, good news - sorry I missed that.
...
>> But check this out, with a modified .32 kernel with the above 2 commints,
>> and a change that reports which inodes were modified:
>>
>> VFS (sda12): inode(s) 1064
>> VFS (sda12): Writes happened before quota was turned on thus quota information is probably inconsistent. Please run quotacheck(8).
>>
>> # find /etc -inum 1064
>> /etc/mtab
> Ah, I'm testing quotas on non-root fs so I was wondering how come people
> hit the warning so often. Now I understand :) For root filesystem on ext4
> we don't have a chance to not see this warning. That being said the warning
> is pretty useless for ordinary users so I guess we should just hide it
> behind #ifdef __DQUOT_PARANOIA and use it for debugging purposes only.
> If noone objects soon, I'll do the change.
Yes, I think it's better that way, otherwise we'll keep getting reports about
how they can't seem to make this warning go away. :)
Thanks,
-Eric
>
> Honza
next prev parent reply other threads:[~2010-04-01 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 15:36 quota reservation fixes for -stable? Eric Sandeen
2010-04-01 8:23 ` Jan Kara
2010-04-01 13:57 ` Eric Sandeen [this message]
2010-04-16 20:37 ` Eric Sandeen
2010-04-19 22:52 ` Jan Kara
2010-04-19 22:56 ` Eric Sandeen
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=4BB4A660.6030609@redhat.com \
--to=sandeen@redhat.com \
--cc=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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.