http://bugzilla.suse.com/show_bug.cgi?id=1043912 http://bugzilla.suse.com/show_bug.cgi?id=1043912#c46 --- Comment #46 from Nikolay Borisov --- (In reply to Frederic Crozat from comment #45)

(In reply to Nikolay Borisov from comment #44)

...

Okay, so the size of the devices is set correctly - it's the total size rounded down. This makes a difference of 4k up. Then this 4k is added to the superblock and as a result it increases by 4k but due to the previous bug in the patches it's still 4k behind the device which won't make the warnings go away. I don't think there is any combination of resize up/down which can make the 2 number synchronize so the options are:

a) You blow and re-create the volume with the last kernel I gave you. The reason why I dare suggest this is i saw your mount point being /mnt/cache and thinking this might be really some temporary storage.

I can do that. But how can we be sure the initial issue is properly fixed ? (again, I hope we don't have customers in the field with similar setup. I wouldn't like to be the support guy telling them they need to recreate their partition ;)

The only way we can be sure is the same as with any other bug - regression tests (I've created an xfstest which I should also extend with the latest information I got from you) and code review. -- You are receiving this mail because: You are on the CC list for the bug.