On Tue, 2020-01-07 at 21:59 -0500, Martin K. Petersen wrote:

Ewan,

quoted

Yes, there are some storage arrays that refuse a READ CAPACITY
command in certain ALUA states so you can't get the new capacity
anyway.

Yep. And some devices will temporarily return a capacity of
0xFFFFFFFF... If we were to trigger a filesystem resize, the results
would be disastrous.

quoted

It might be nice to improve this, though, there are some cases now
where we set the capacity to zero when we revalidate and can't get the
value.

If you have a test case, let's fix it.

This happens with NVMe fabric devices, I thought.  I'll check.