On Sun, 2020-08-30 at 08:10 -0500, Robert Nichols wrote:
On 8/30/20 3:01 AM, Philip Rhoades wrote:
> Samuel,
>
>
> On 2020-08-30 17:12, Samuel Sieb wrote:
> > On 8/30/20 12:07 AM, Philip Rhoades wrote:
> > > that it would take weeks! So unless someone can suggest a faster method
of fixing the partition (mainly just as an exercise now) or at least just working out what
is wrong with it, I guess I will just have to re-create the partition?
> >
> > Since you have a very recent full backup, I would recommend just
> > reformatting the partition. If the damage is that extensive, it's not
> > worth trying to fix it.
>
> You are probably right - it would be an interesting exercise if it could be done
though . .
There is no point in even trying. "Multiply claimed blocks" is an unrecoverable
situation. Sure, each block can be cloned to give each file its own copy. The filesystem
will now be consistent, but the some files will have corrupted content. Only one of those
files (probably the newest one) claiming the block will hold its correct data. It's
the job of _fsck_ to make the filesystem consistent, and not necessarily to preserve user
data in the process. Having a consistent filesystem with corrupted file content is
arguably a worse situation than a filesystem with known, detectable corruption.
I always used to tell people that "an empty filesystem is consistent".
poc