Skip to content

dm vdo recovery: improve old journal format handling

Matthew Sakai dm-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2dm vdo: abort loading dirty VDO with the old recovery journal formatdrivers/md/dm-vdo/dm-vdo-target.c drivers/md/dm-vdo/repair.c+24 -40 replies
2/2dm vdo: force read-only mode for a corrupt recovery journaldrivers/md/dm-vdo/repair.c drivers/md/dm-vdo/status-codes.c drivers/md/dm-vdo/status-codes.h+24 -190 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] dm vdo recovery: improve old journal format handling

Some older out-of-tree versions of vdo use a format for recovery journal entries that cannot be processed by the current recovery code. For vdo volumes created with these older versions, reduce the likelihood of entering read-only mode.

This will ease the transition of older volumes to the in-kernel dm-vdo target.

Susan LeGendre-McGhee (2):
dm vdo: abort loading dirty VDO with the old recovery journal format dm vdo: force read-only mode for a corrupt recovery journal

 drivers/md/dm-vdo/dm-vdo-target.c | 24 +++++++++++++++++-
 drivers/md/dm-vdo/repair.c        | 41 +++++++++++++++++--------------
 drivers/md/dm-vdo/status-codes.c  |  2 +-
 drivers/md/dm-vdo/status-codes.h  |  2 +-
 4 files changed, 47 insertions(+), 22 deletions(-)
Signature · 1 line
2.45.2