That's a pity.
Please reconsider this: Imagine a storage cluster mainly used for "archival of data on spinning media". In such a case, one would set up a round-robin scheduler to fill the storage devices (bricks) one by one, and one would "freeze" full bricks by setting them read-only so modification will be no longer possible. I think such a behaviour would make sense.
Steffen, the schedulers already ensure that 'full' bricks are not scheduled new files. though the read-only translator awareness in unify will help certain cases, the case you mentioned is already handled by the schedulers. thanks, avati -- Anand V. Avati
