Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #226337

Re: Disks renamed after update to 'testing'...?

From David Christensen <dpchrist@holgerdanske.com>
Newsgroups linux.debian.user
Subject Re: Disks renamed after update to 'testing'...?
Date 2020-08-20 22:40 +0200
Message-ID <AFZvP-40t-1@gated-at.bofh.it> (permalink)
References <AEX33-7kr-1@gated-at.bofh.it> <AFE81-7Xs-3@gated-at.bofh.it> <AFNuF-5fj-1@gated-at.bofh.it> <AFUPw-1d5-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 2020-08-20 08:32, rhkramer@gmail.com wrote:
> On Thursday, August 20, 2020 03:43:55 AM tomas@tuxteam.de wrote:
>> Contraty to the other (very valid) points, my backups are always on
>> a LUKS drive, no partition table. Rationale is, should I lose it, the
>> less visible information the better. Best if it looks like a broken
>> USB stick. No partition table looks (nearly) broken :-)

I always use a partition table, to reduce the chance of confusing 
myself.  ;-)


> I have two questions:
> 
>     * I suppose that means you create the LUKS drive on, e.g., /dev/sdc rather
> than, for example, /dev/sdc<n>?  (I suppose that should be easy to do.)
> 
>     * But, I'm wondering, how much bit rot would it take to make the entire
> backup unusable, and what kind of precautions do you take (or could be taken)
> to avoid that?

I have been pondering bit-rot mitigation on non-checksumming filesystems.


Some people have mentioned md RAID.  tomas has mentioned LUKS.  I 
believe both of them add checksums to the contained contents.  So, 
bit-rot within a container should be caught by the container driver.  In 
the case of md RAID, the driver should respond by fetching the data from 
another drive and then dealing with the bad block(s); the application 
should not see any error (?).  I assume LVM RAID would respond like md 
RAID (?).  In the case of LUKS, the driver has no redundant data (?) and 
will have no choice but to report an error to the application (?).  I 
would guess LVM non-RAID would behave similarly (?).


For all three -- md, LUKS, LVM -- I don't know what happens for bit rot 
outside the container (e.g. in the container metadata).


David

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Disks renamed after update to 'testing'...? "hobie of RMN" <hobie@rumormillnews.com> - 2020-08-18 01:50 +0200
  Re: Disks renamed after update to 'testing'...? David Christensen <dpchrist@holgerdanske.com> - 2020-08-18 03:30 +0200
    Re: Disks renamed after update to 'testing'...? "hobie of RMN" <hobie@rumormillnews.com> - 2020-08-18 06:10 +0200
      Re: Disks renamed after update to 'testing'...? john doe <johndoe65534@mail.com> - 2020-08-18 08:40 +0200
        Re: Disks renamed after update to 'testing'...? didier gaumet <didier.gaumet@gmail.com> - 2020-08-18 10:30 +0200
          Re: Disks renamed after update to 'testing'...? Nicolas George <george@nsup.org> - 2020-08-18 11:40 +0200
            Re: Disks renamed after update to 'testing'...? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-08-18 12:20 +0200
          Re: Disks renamed after update to 'testing'...? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-08-18 11:40 +0200
      Re: Disks renamed after update to 'testing'...? David Christensen <dpchrist@holgerdanske.com> - 2020-08-18 12:10 +0200
  Re: Disks renamed after update to 'testing'...? "Rick Thomas" <rick.thomas@pobox.com> - 2020-08-18 10:40 +0200
    Re: Disks renamed after update to 'testing'...? Urs Thuermann <urs@isnogud.escape.de> - 2020-08-18 20:40 +0200
      Re: Disks renamed after update to 'testing'...? David Christensen <dpchrist@holgerdanske.com> - 2020-08-18 22:00 +0200
        Re: Disks renamed after update to 'testing'...? Urs Thuermann <urs@isnogud.escape.de> - 2020-08-19 08:10 +0200
          Re: Disks renamed after update to 'testing'...? David Christensen <dpchrist@holgerdanske.com> - 2020-08-19 10:40 +0200
            Re: Disks renamed after update to 'testing'...? Urs Thuermann <urs@isnogud.escape.de> - 2020-08-19 12:10 +0200
              Re: Disks renamed after update to 'testing'...? David Christensen <dpchrist@holgerdanske.com> - 2020-08-19 23:50 +0200
                Re: Disks renamed after update to 'testing'...? <tomas@tuxteam.de> - 2020-08-20 09:50 +0200
                Re: Disks renamed after update to 'testing'...? Joe <joe@jretrading.com> - 2020-08-20 12:20 +0200
                Re: Disks renamed after update to 'testing'...? rhkramer@gmail.com - 2020-08-20 17:40 +0200
                Re: Disks renamed after update to 'testing'...? David Christensen <dpchrist@holgerdanske.com> - 2020-08-20 22:40 +0200
                Re: Disks renamed after update to 'testing'...? Dan Ritter <dsr@randomstring.org> - 2020-08-20 23:40 +0200
                Re: Disks renamed after update to 'testing'...? Andy Smith <andy@strugglers.net> - 2020-08-21 00:00 +0200
                Re: Disks renamed after update to 'testing'...? David Christensen <dpchrist@holgerdanske.com> - 2020-08-21 11:50 +0200
                Re: Disks renamed after update to 'testing'...? <tomas@tuxteam.de> - 2020-08-21 10:40 +0200
      Re: Disks renamed after update to 'testing'...? Urs Thuermann <urs@isnogud.escape.de> - 2020-08-19 09:00 +0200

csiph-web