BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Backing up the entire software installation
- Subject: [Discuss] Backing up the entire software installation
- From: richard.pieri at gmail.com (Rich Pieri)
- Date: Thu, 25 Oct 2018 16:57:22 -0400
- In-reply-to: <6cd23aac-1d96-90da-159c-386d18c1389b@gmx.com>
- References: <CAPnB49Fca+-AdFDF0WHz6Mo5Qght98e9JJ17m-iYz-A4P1XL1A@mail.gmail.com> <20181025171200.GD22674@bladeshadow.org> <5bd2261c.1c69fb81.f5f45.cff7@mx.google.com> <6cd23aac-1d96-90da-159c-386d18c1389b@gmx.com>
On Thu, 25 Oct 2018 16:33:22 -0400 Marco Milano <marco.milano at gmx.com> wrote: > > Avoid ext4 for anything important if at all possible. > > Why? Because there is a flaw (or possibly several) in the ext4 extents mechanism which, when tripped, causes extent corruption and data loss. fsck will *not* repair an ext4 filesystem in this state. The only "fix" is to create a new filesystem with mkfs. -- Rich Pieri
- References:
- [Discuss] Backing up the entire software installation
- From: nancythewriter7 at gmail.com (Nancy Allison)
- [Discuss] Backing up the entire software installation
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] Backing up the entire software installation
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Backing up the entire software installation
- From: marco.milano at gmx.com (Marco Milano)
- [Discuss] Backing up the entire software installation
- Prev by Date: [Discuss] Backing up the entire software installation
- Next by Date: [Discuss] Backing up the entire software installation
- Previous by thread: [Discuss] Backing up the entire software installation
- Next by thread: [Discuss] Backing up the entire software installation
- Index(es):
