On Sun, Nov 16, 2014 at 10:46 PM, Fred Liu <[email protected]> wrote:
> We just met the case that usedbydataset is bigger than refquota. It > prevents users from removing files while the file system is full. > Do you have the fix for bug 4950? commit 4bb73804952172060c9efb163b89c17f56804fe8 Author: Matthew Ahrens <[email protected]> Date: Mon Jul 7 11:49:36 2014 -0800 4950 files sometimes can't be removed from a full filesystem Reviewed by: Adam Leventhal <[email protected]> Reviewed by: George Wilson <[email protected]> Reviewed by: Sebastien Roy <[email protected]> Reviewed by: Boris Protopopov <[email protected]> Approved by: Dan McDonald <[email protected]> > I guess it could come from quota setting(we set both quota and refquota).. > Normally we have the equation -- “usedbydataset” = “userdata” + > “metadata”. > > Will refquota also constraint metadata? > All of these (used, usedby*, refer, quota, refquota) include metadata (e.g. indirect blocks). In this case, usedbydataset is only 98107 bigger than refquota(zfs get –Hp > …). > FYI, the "refquota" property constrains the "referenced" property. --matt It is really trivial if we don’t feed “-Hp”. > > zfs get quota,refquota,usedbysnapshots,usedbydataset,used > cn03/3/is8169am > > NAME PROPERTY VALUE SOURCE > > cn03/3/is8169am quota 55G local > > cn03/3/is8169am refquota 50G local > > cn03/3/is8169am usedbysnapshots 3.24G - > > cn03/3/is8169am usedbydataset 50.0G - > > cn03/3/is8169am used 53.2G - > > > > For metadata is variable, I think it should not be accounted in refquota. > Correct? > > > > > > Thanks. > > > > Fred > > _______________________________________________ > developer mailing list > [email protected] > http://lists.open-zfs.org/mailman/listinfo/developer > >
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
