Hi Tomas, Thanks for recategorizing the bug and applying the version. I was getting caught up and see you already did this.
Just wanted to add a few points from additional testing I've been doing. > I can't replicate this by damaging /var in any other way. I've tried filling the volume up until no writes can be performed, but requesting a new lease behaves as normal. I think swap has something to do with this since the file system is still mounted R/W. I've also tried deleting the leases file and chmoding that directory to RO. It appears that storage containing the OS has to truly disconnect for some time and cause the volume to be marked as RO. > I agree that this could probably be replicated on any virtualization platform. I'll test on virtualbox and KVM and let you know if anything is different there. Thanks, let me know if I can answer any questions. -Mark
