From: Michael Tokarev <mjt@tls.msk.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] quota: Turn quotas off when remounting read-only
Date: Thu, 07 Feb 2008 22:27:27 +0300 [thread overview]
Message-ID: <47AB5B9F.8090302@msgid.tls.msk.ru> (raw)
In-Reply-To: <20080207103655.14ce8512.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 7 Feb 2008 15:37:21 +0100 Jan Kara <jack@suse.cz> wrote:
>
>> Turn off quotas before filesystem is remounted read only. Otherwise quota will
>> try to write to read-only filesystem which does no good... We could also just
>> refuse to remount ro when quota is enabled but turning quota off is consistent
>> with what we do on umount.
[a nice one-liner snipped]
> Cool. And this is applicable to 2.6.23, 2.6.22 and even earlier, isn't it?
Provided the amount of time this issue exists, I don't think it's worth
to push it to -stable. It's an oooooooold, issue, which happens quite
rarely, and no one bothered to report it so far... But it's not my
call... ;)
But... I'm thinking about this scenario:
# mount /data
# quotaon /data
(some maintenance stuff to be planned)
# mount -o remount,ro /data
(do backup etc)
# mount -r remount,rw /data
at this point, it's expected that quota on /data is enabled.
After this patch, it's not anymore...
I think it's more usual scenario than mine (umount instead of
remount-rw). And this change will break it. So I'm not sure
what really to do here. Probably refusing remount-ro if quota
is on is better... it's annoying for sure, but at least it's
explicit, and avoids the handg too.
/mjt
next prev parent reply other threads:[~2008-02-07 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 14:37 [PATCH] quota: Turn quotas off when remounting read-only Jan Kara
2008-02-07 18:36 ` Andrew Morton
2008-02-07 19:27 ` Michael Tokarev [this message]
2008-02-11 12:39 ` Jan Kara
2008-02-15 14:10 ` Jan Engelhardt
2008-02-15 14:21 ` Michael Tokarev
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=47AB5B9F.8090302@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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.