[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <47B59FE5.9000506@msgid.tls.msk.ru>
Date: Fri, 15 Feb 2008 17:21:25 +0300
From: Michael Tokarev <mjt@....msk.ru>
To: Jan Engelhardt <jengelh@...putergmbh.de>
CC: Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH] quota: Turn quotas off when remounting read-only
Jan Engelhardt wrote:
> On Feb 11 2008 13:39, Jan Kara wrote:
>>> 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...
>> Yes, it previously accidentally worked this way (for an year or so,
>> before that we refused to remount read-only). Hmm, but maybe we could
>> somehow tweak quotas to be turned on when remounting read-write again.
>> We have all the information we need at the time of remounting read-only
>> so we could store it and use it later when remounting read-write. I'll have
>> a look into that.
>
> Maybe it is possible to leave quota on all times, so that the
> reporting quota ioctls continue to work even in ro mode?
Well, that'd be the best approach imho (plus check if all
ioctls which try to modify quotas fails with EROFS as
appropriate).
But the problem really is that it's unknown at this time
where it fails in the first place. I can't reproduce my
hang "on demand" (mount-ro followed with umount when quotas
are turned on, with ext3fs - umount never finishes), yet
it has biten me for several times already. So it must be
something rare, some small race maybe, which is difficult
to find... Yet it finds itself at the most inappropriate
moment. ;) I already learned to turn the quota off before
doing something with a filesystem, but sometimes I'm
forgetting this, and the result is always the same... ;)
Oh well.
/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists