[disk/max_diskspace] fails on disks even though there's only 1GB of unaccounted space

[Jeff Lane ]

I found two instances where max diskspace failed. On the first system, it found that 249 of 250 GB had been allocated to Ubuntu but it failed because that's less than 0.15 (arbitrary number?) the difference there is actually something like 0.014.

Found it failing on another system with a 36.4GB disk where only 35.4GB were allocated. This could easily occur if that remaining 1GB was used for hardware RAID overhead or other purposes...

[Daniel Manrique (roadmr)]

Remilestoning to 0.13.x as 0.13.6 was released yesterday :)

[Brendan Donegan (brendan-donegan)]

This is a similar problem to the one with the memory test - how do you know what this unaccounted for memory is being used for? We could just arbitrarily increase the threshold, but that's just a bandaid.

I don't know that I'd consider this such a huge problem if it's only happening on a couple of machines though.

[Brendan Donegan (brendan-donegan)]

To properly triage this I'd need to find out which system this is occuring on.

[Jeff Lane  (bladernr)]

Since I can't add private comments, I've created a private duplicate bug and linked it to this one. The failing systems were all done at a customer site, but 16 or 18 failed the this test.

That being said, I wonder about the value of this test as far as hardware certification goes anyway. The only thing it really tests that the default partitioning scheme is sane, which is a software/QA concern, not so much a hardware concern. We have other tests to validate that storage hardware works and the filesystem isn't fragile, so this test could probably just be removed from the whitelists.

[Jeff Lane  (bladernr)]

I should add that I filed this initially after two instances of failure noted, but after reviewing all the results, the overwhelming majority failed.

[Daniel Manrique (roadmr)]

Marking Won't Fix, since per https://bugs.launchpad.net/checkbox/+bug/1031997 this test will be removed soon.