I have tested that command manually. I think it is because "e2fsck" failed
my own image.
root@controller:/data/stack/glance/images# e2fsck -fp
bfd0d705-281c-4ee1-a896-bf4c0d6c1f94
e2fsck: Bad magic number in super-block while trying to open
bfd0d705-281c-4ee1-a896-bf4c0d6c1f94
bfd0d705-281c-4ee1-a896-bf4c0d6c1f94:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Is it right? How can it be fixed?
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
