On Jun 01 2016, Nikolaus Rath <nikol...@rath.org> wrote: > Hello, > > For one of my btrfs volumes, btrfsck reports a lot of the following > warnings: > > [...] > checking extents > bad extent [138477568, 138510336), type mismatch with chunk > bad extent [140091392, 140148736), type mismatch with chunk > bad extent [140148736, 140201984), type mismatch with chunk > bad extent [140836864, 140865536), type mismatch with chunk > [...] > > Is there a way to discover which files are affected by this (in > particular so that I can take a look at them before and after a btrfsck > --repair)?
Hmm. Anyone? Is there really no way to figure out what might be affected if I attempt a repair? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- 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