Comment 6 for bug 1415077

Ted, thanks for your response, and sorry for the spam.

Can you just verify that this specific bit seems correct:
 | On that derived image, I see 'resize2fs -P' numbers like:
 | trusty: 274500
 | utopic: 358400
 | vivid: 358400
 | The 83900 blocks out of a 358400 seems significant (23% of the fs size),
 | and results in the image appearing full on utopic/vivid, even though
 | a mount and df show only 74% full.

Note, that :
  'df' reports the fs is 74% full,
  dumpe2fs reports the filesystem is 358400 blocks,
  resize2fs -P reports that the minimum size is 358400 blocks.

Ie, per resize2fs -P says we can't shrink this 1400M filesystem at all, which has greater than 300M available.

I'm willing to accept that this is academic, and an invalid bug, but I just wanted to clarify as the above seems wrong.