dm vdo: abort loading dirty VDO with the old recovery journal format
authorSusan LeGendre-McGhee <slegendr@redhat.com>
Fri, 19 Jul 2024 21:52:32 +0000 (17:52 -0400)
committerMikulas Patocka <mpatocka@redhat.com>
Wed, 21 Aug 2024 11:11:34 +0000 (13:11 +0200)
commitf3ff668352c59db2c0ab47f2e86488a70694ed57
treeaecba80da9fd85284d5f925e8bbf3034f05ebd88
parent47874c98dc0873aad65259d09f9b9029e97429e3
dm vdo: abort loading dirty VDO with the old recovery journal format

Abort the load process with status code VDO_UNSUPPORTED_VERSION
without forcing read-only mode when a journal block with the
old format version is detected.

Forcing the VDO volume into read-only mode and thus requiring
a read-only rebuild should only be done when absolutely necessary.

Signed-off-by: Susan LeGendre-McGhee <slegendr@redhat.com>
Signed-off-by: Matthew Sakai <msakai@redhat.com>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
drivers/md/dm-vdo/dm-vdo-target.c
drivers/md/dm-vdo/repair.c