Hi urle,

I assume you understand the difference in regard to deduplication for the quota policy filesize ?

happy new year

Rainer

I assume you understand the difference in regard to deduplication for the

quota policy filesize ?

Filesize quota will not reflect space savings due to dedupe? I think this

was reason of my problems with block policy. User and tree quota were

calculated and shown correctly but writes were denied even with lots of

reserved space (5MB used and shown with 80MB quota but 'quota exceeded'

errors when writing).

And EMC prefers filesize policy with dedupe - at least they told me.

yes, with quota policy block the compressed size is used for quta calcs and with filesize the original size

I dont think we prefer either one - its up to the customer how he wants the quotas calculated

I dont think we prefer either one - its up to the customer how he wants

the quotas calculated

In one of my SR I got following advice:

If the bulk of the traffic to this dm now and in the future will be cifs.

And you are using dedupe then you should consider changing the quota policy

to filesize,recalculating quotas and upgrading the NAS code for the dedupe

and tree quota issue.

And after doing the change from block to filesize the numbers look more

reasonable for my customers. Small files (eg cookies) count only with their

size - not with 8k per file.

... but it was a long way to change and recalc ~350 treequotas:(

Thank you and Peter for your help!