Description of problem: Version-Release number of selected component (if applicable): 3.3.0-0.1 How reproducible: always Steps to Reproduce: 1. Create two SDs. SD1, SD2. 2. Create quota, with limit SD1 20GB, SD2 5GB. 3. Set DC to enforced mode. 4. Create disk 10GB disk on SD1. 5. Move disk from SD1 to SD2. Actual results: Success. Expected results: Fail, not enough storage resources Additional info:
Ondra, this is working by design. You need to understand that quota is an upper limit (max) constraint, and not a lower one (min). It's abstracted from the physical entities, which may change over time. For example, as a university admin, I may be able to define students quota of 50 GB, even if my storage has only 30 GB. Later on I may increase this storage regardless of quota allocations which should still function as defined. For the same reason, on a storage with 10 GB, I may define students quota of 6 GB, and faculty quota of 6 GB. It's an upper limit and the responsibility of the admin to assure relevant resources are available when needed.
I did not decribe it right, sorry for that. For claryfing: Steps to reproduce are same. The issue is not that storage has not enough resources but quota has not. So the results should be: Actual results: Succeeded moving 10 GB disk to a DC enfocing a 5 GB quota. Expected results: Fail, Quota exceeded
3.2 has been released