[ Resend due to accidental HTML subpart ] On Fri, May 5, 2017 at 7:57 AM, Sage Weil <sage@xxxxxxxxxxxx> wrote: > > On Fri, 5 May 2017, Dan van der Ster wrote: > > On Fri, May 5, 2017 at 4:36 PM, Dan van der Ster <dan@xxxxxxxxxxxxxx> wrote: > > > Hi all, > > > > > > It would be really nice if for Luminous client quotas were always > > > enabled -- it should be impossible to disable quota enforcement on the > > > client side. > > > > > > From the looks of things, the patch to remove client_quota and > > > client_quota_df would be trivial. > > > Is there some reason we need to leave that optional? > > > > PR: 14978 > > This seems reasonable to me. Client can of course run modified code so > it's not really "secure" in that sense but it's certainly inconvenient to > circumvent. I'm sure John will comment on this once he gets back from vacation, but there were some reasons not to enable it by default when this was discussed by the team last fall. I think it was combined concern about the lack of server-side enforcement and (more importantly) not wanting to provide default experiences which differ across the userspace and kernel clients. -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
