On Mon, Aug 03, 2015 at 11:51:58AM +0300, Vladimir Stavrinov wrote: > On Mon, Aug 03, 2015 at 09:53:03AM +0300, Lars Wirzenius wrote: > > > fsck does, indeed, not remove references to missing chunks. It's a > > missing feature. That feature will be implemented when someone has the > > time and inclination to do it. > > > > Asking why it isn't done yet does not make it happen faster, I'm > > afraid. > > The question was not "why it isn't done YET", but why they are not > removing at all, thinking it is a bug. And Yes, if You treat bug as > "missing feature", then there are less chances that "it happen faster" > to fix it.
I don't understand what you're trying to say. > OK, it is up to You how to treat it and what to do or not to do. But the > question remains about "checksum whole-file checksum mismatch". Is this > problem related to non-existent chunks, as they appear all together, one > next to other? In other words, should the both problems be solved with > the same single fixing, or they are subject for different bug fixings? If a file is missing a chunk, then it's data cannot be restored correctly, and the checksum of the restored data does not match the original file. That's what it means, and yes, it's related to the missing chunk. -- sic transit disci mundi, ergo obnam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
