Comment 32 for bug 824089

For the record I've just tested linux-image-3.2.0-030200rc2-generic_3.2.0-030200rc2.201111151435 and the bug is still present. This is still on XenServer 5.6 SP2; I'll try to test on a XS 6 install later. (Lucid does work on both versions; the problem is only with Oneiric.)

Stefan: I hadn't spotted the capacity change discrepancy, but on my latest test with the above kernel I do get capacity change messages for all three disks:

[ 0.492436] blkfront: xvda: barrier: enabled
[ 0.495160] xvda: unknown partition table
[ 0.496794] blkfront: xvdb: barrier: enabled
[ 0.498990] xvdb: unknown partition table
[ 0.499217] Setting capacity to 524288
[ 0.499225] xvda: detected capacity change from 0 to 268435456
[ 0.499911] blkfront: xvdc: barrier: enabled
[ 0.501937] xvdc: unknown partition table
[ 0.502127] Setting capacity to 12582912
[ 0.502136] xvdb: detected capacity change from 0 to 6442450944
[ 0.507102] Setting capacity to 1024000
[ 0.507117] xvdc: detected capacity change from 0 to 524288000

These disks are all XenServer's NFS-backed virtual disks. The bug does NOT occur if the root filesystem is on local storage.