Incremental fsck
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · Al Boldi
Even after a black-out shutdown, the corruption is pretty minimal, using ext3fs at least. So let's take advantage of this fact and do an optimistic fsck, to assure integrity per-dir, and assume no external corruption. Then we release this checked dir to the wild (optionally ro), and check the next. Once we find external inconsistencies we either fix it unconditionally, based on some preconfigured actions, or present the user with options.
Maybe we can know the changes that need to be done in order to fix the filesystem. Let's record this information in - eh - let's call it a journal!
Quoted 9 lines · Bodo Eggert
Quoted 7 lines · Al Boldi
Even after a black-out shutdown, the corruption is pretty minimal, using ext3fs at least. So let's take advantage of this fact and do an optimistic fsck, to assure integrity per-dir, and assume no external corruption. Then we release this checked dir to the wild (optionally ro), and check the next. Once we find external inconsistencies we either fix it unconditionally, based on some preconfigured actions, or present the user with options.
Quoted 3 lines
Maybe we can know the changes that need to be done in order to fix the filesystem. Let's record this information in - eh - let's call it a journal!
Don't mistake data=journal as an fsck replacement.
Thanks!
--
Al