summaryrefslogtreecommitdiffstats
path: root/drivers/md/dm-vdo/vdo.h
diff options
context:
space:
mode:
authorMatthew Sakai <msakai@redhat.com>2023-11-16 21:08:05 -0500
committerMike Snitzer <snitzer@kernel.org>2024-02-20 13:43:15 -0500
commit4fa98386be2ff32f18b939d3bf5f6841d638fccd (patch)
tree159d34e2465e7f1cd7e8a6d6a9dc8d4e389ef4e8 /drivers/md/dm-vdo/vdo.h
parent95a72357688803736bf60db973cbf94c0ff3a6da (diff)
downloadlinux-stable-4fa98386be2ff32f18b939d3bf5f6841d638fccd.tar.gz
linux-stable-4fa98386be2ff32f18b939d3bf5f6841d638fccd.tar.bz2
linux-stable-4fa98386be2ff32f18b939d3bf5f6841d638fccd.zip
dm vdo: add repair of damaged vdo volumes
When a vdo is restarted after a crash, it will automatically attempt to recover from its journals. If a vdo encounters an unrecoverable error, it will enter read-only mode. This mode indicates that some previously acknowledged data may have been lost. The vdo may be instructed to rebuild as best it can in order to return to a writable state. Although some data may be lost, this process will ensure that the vdo's own metadata is self-consistent. Co-developed-by: J. corwin Coburn <corwin@hurlbutnet.net> Signed-off-by: J. corwin Coburn <corwin@hurlbutnet.net> Co-developed-by: Michael Sclafani <dm-devel@lists.linux.dev> Signed-off-by: Michael Sclafani <dm-devel@lists.linux.dev> Co-developed-by: Sweet Tea Dorminy <sweettea-kernel@dorminy.me> Signed-off-by: Sweet Tea Dorminy <sweettea-kernel@dorminy.me> Signed-off-by: Matthew Sakai <msakai@redhat.com> Signed-off-by: Mike Snitzer <snitzer@kernel.org>
Diffstat (limited to 'drivers/md/dm-vdo/vdo.h')
0 files changed, 0 insertions, 0 deletions