As of historical data, I'd rather like to see on-the-fly aging/releasing of the oldest PFS snapshots or better more fine grained structures (with some notifications to admins probably). Have no idea of how difficult is it to implement. So, if a user tried to overwrite a 10Gig file 100 times in a row he will just loose the oldest versions of it, not a big deal for me.
/dennis On Tue, Sep 28, 2010 at 4:28 PM, Sdävtaker <[email protected]> wrote: > I think historical data should not affect user quota since user is > unable to clean up his own historical data. > Historical data should be seen as administrative overhead, there is a > need to know some metric about the historical data so cleanup can be > automatized to avoid the scenario where users "got" space but it > doesnt exist phisically in the box. > Damian > > On Tue, Sep 28, 2010 at 06:25, Antonio Huete Jimenez > <[email protected]> wrote: > > One of my concerns here is, as the historical data is taking up more > > and more disk space without being taken in account, it could be the > > case that there's not enough space to satifisfy user's disk needs even > > if they're not reaching the quotas. > > > > How would that case be handled? Should the sysadmin take this in account? > > > > I'm not 100% sure that the historical data shouldn't count on the total > sum. > > > > Cheers, > > Antonio Huete > > > > > > -- > http://dfbsd.trackbsd.org.ar > -- Dennis Melentyev
