From: Gregory (Grisha) Trubetskoy (grisha_at_ispol.com)
Date: Tue 09 Nov 2004 - 19:14:10 GMT
On Tue, 9 Nov 2004, Gregory (Grisha) Trubetskoy wrote:
> The key here is that a file belongs to a context other than 0. The actual xid
> doesn't matter.
> So perhaps another fs flag would solve this. (As far as I understand there is
> no xid flag right now, IATTR_XID is an artifact of whether MS_TAGXID is
> If I am in context 0 don't bother with counters.
> If I am in context X and removing a file, then:
> If the file belongs to a context other than 0:
> decrement counter
> If I am in context X and creating a file:
> Set the xid flag to 1
BTW, upon some more thinking - this would work even without an additional
flag, the iunlink could serve this purpose:
if in ctx X and deleting a file:
if not iunlink:
It looks like the disk limits do not allow you to get above the maximum,
so it won't be possible to get more space than initially alloted by
deleting regular (mutable) files.
This sounds simple enough for me to put a patch together - the question is
- is this worth the effort, or there is something coming that will solve
this problem more elegantly?
The original problem being that tools like dump (and rsync?) do not deal
with XID-tagged file.
Vserver mailing list