> Is there some way to fix this corruption? I noticed what looks like
> the same problem in an earlier message on the list ("btrfs unmountable
> after failed suspend", February 7), but with no resolution. I have
> offline backups, but recovering those in their entirety will take some
> time, so a solution that doesn't require wiping the entire FS would be
> preferred.
I did some further investigation into the problem, and I have
determined the problematic directory (by seeing where `ls -R` hangs).
If I skip the corrupt directory, everything works properly, but
attempting to list its contents causes the entire volume to stop
responding.
At this point I'd like to simply unlink the corrupt directory (without
enumerating it). Is that possible, or should I just image the volume
minus the corrupt directory and recreate my fs?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
