jim owens wrote:
> Quota accounting and disk space used for the original file will
> be as if there were 0 reflinks. Quota accounting and disk space
> reported for the new reflink file is filesystem specific and may
> or may not include shared disk space.
One little thing:
If the original file is deleted,
1. The data must still be accounted at least once.
2. After deleting the original, the space must not be charged to
the owner of the original file if different from the owners of
reflinks which remain, because that would be a quota attack.
Less important:
3. The combination of 1 and 2 probably shouldn't cause the quota
charge of other users (who created reflinks and aren't the
original file owner) to increase as it might push them over their
quota, in a way that's difficult for them to know beforehand.
One way to satisfy that is for the reflink's data to be charged at
least once to each distinct owner who references that data. Maybe it
can be done by charging it when the owner of a new reflink is
different from the original, and something appropriate during chown.
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
