Boston Linux & UNIX was originally founded in 1994 as part of The Boston Computer Society. We meet on the third Wednesday of each month at the Massachusetts Institute of Technology, in Building E51.

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] Backing up the entire software installation

On Thu, 25 Oct 2018 18:50:16 -0400 (EDT)
Robert Krawitz <rlk at> wrote:

> Are you referring to the unwritten/delayed extents bug
> (e. g.  That was
> fixed over 3 years ago
> (

One of my encounters with extent corruption was probably this, but I've
had other encounters with corrupt extents after this fix was applied.
The most recent was summer or fall 2017 on RHEL 7.3 and deliberate
because we were trying to identify a different ext4 corruption bug
which turned out to be two bugs, one in ext4 and one in VFS.

My recommendation not to use ext4 is less about the corruption
problems, though, and more about the inability to identify and repair
the damage. fsck cannot tell you what files are affected because that
information is what's damaged. Since it cannot identify what's affected
it cannot effect repairs, either. You have to wipe and restore from
backups made prior to the corruption.

Rich Pieri

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /