Public bug reported:
reproducible issue.
After creating a new LV --type raid5, mkfs.ext4 and rsync the backup the
filesystem will corrupt if i extend the lv using lvconvert --stripes N vg/lv. I
monitor the cpy%sync with lvs and reboot well after 100%, but the fs wont mount
and file -s /dev/dm-N says "data"
IMHO lvconvert --stripes N should refuse to run on --type raid5 until
resolved.
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1787769
Title:
lvconvert stripes N of lv type raid5 results in dead filesystem
Status in lvm2 package in Ubuntu:
New
Bug description:
reproducible issue.
After creating a new LV --type raid5, mkfs.ext4 and rsync the backup the
filesystem will corrupt if i extend the lv using lvconvert --stripes N vg/lv. I
monitor the cpy%sync with lvs and reboot well after 100%, but the fs wont mount
and file -s /dev/dm-N says "data"
IMHO lvconvert --stripes N should refuse to run on --type raid5 until
resolved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1787769/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
