On Fri, Oct 3, 2014 at 9:54 AM, Josef Bacik <jba...@fb.com> wrote: > We can deal with corrupt items by deleting them in a few cases. Fsck can > easily > recover from a missing extent item or a dir index item. So if we notice a > item > is completely bogus and it is of a key that we know we can repair then just > delete it and carry on. Thanks, > > Signed-off-by: Josef Bacik <jba...@fb.com> > --- > cmds-check.c | 45 > +++++++++++++++++++++++++++++++ > tests/fsck-tests/005-bad-item-offset.img | Bin 0 -> 398336 bytes > 2 files changed, 45 insertions(+) > create mode 100644 tests/fsck-tests/005-bad-item-offset.img >
It looks like tests/fsck-tests/005-bad-item-offset.img was added unintentionally to this patch. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
