Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #247349
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: backing up backups |
| Date | 2022-04-19 00:50 +0200 |
| Message-ID | <EdIlY-9Ewk-1@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <EbO2u-8vaf-27@gated-at.bofh.it> <EbS65-8xyG-5@gated-at.bofh.it> <EbY1P-8BoS-1@gated-at.bofh.it> <Ec25r-8DPa-5@gated-at.bofh.it> <EdFR7-9Dbo-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 4/18/22 13:06, Default User wrote:
> Finally, fun fact:
> Many years ago, at a local Linux user group meeting, Sun Microsystems put
> on a demonstration of their ZFS filesystem. To prove how robust it was,
> they pulled the power cord out of the wall socket on a running desktop
> computer. Then they plugged the cord back in and re-booted, with no
> problems! Yes, I was impressed.
I bumped the USB cable of an external HDD while doing a ZFS incremental
replication from my server to a backup disk. The backup pool was corrupted:
2022-03-28 18:16:25 toor@f1 ~
# zpool status -v z6000b
pool: z6000b
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: scrub repaired 0 in 0 days 09:36:15 with 0 errors on Mon Mar 28
00:09:09 2022
config:
NAME STATE READ WRITE CKSUM
z6000b ONLINE 0 0 0
gpt/z6000b.eli ONLINE 0 0 0
cache
gpt/z60a.eli ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
<metadata>:<0x0>
<metadata>:<0x39>
I bought a SATA 6 Gbps drive rack:
https://www.startech.com/en-us/hdd/drw150satbk
destroyed the backup pool, recreated the backup pool, and did a full
replication.
David
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
backing up backups Default User <hunguponcontent@gmail.com> - 2022-04-11 05:00 +0200
Re: backing up backups David <bouncingcats@gmail.com> - 2022-04-11 05:20 +0200
Re: backing up backups Default User <hunguponcontent@gmail.com> - 2022-04-11 06:00 +0200
Re: backing up backups David Christensen <dpchrist@holgerdanske.com> - 2022-04-11 06:50 +0200
Re: backing up backups <tomas@tuxteam.de> - 2022-04-11 07:20 +0200
Re: backing up backups David Christensen <dpchrist@holgerdanske.com> - 2022-04-11 18:10 +0200
Re: backing up backups Default User <hunguponcontent@gmail.com> - 2022-04-13 18:30 +0200
Re: backing up backups David Christensen <dpchrist@holgerdanske.com> - 2022-04-13 22:50 +0200
Re: backing up backups Default User <hunguponcontent@gmail.com> - 2022-04-14 05:10 +0200
Re: backing up backups David Christensen <dpchrist@holgerdanske.com> - 2022-04-14 09:30 +0200
Re: backing up backups Default User <hunguponcontent@gmail.com> - 2022-04-18 22:10 +0200
Re: backing up backups David Christensen <dpchrist@holgerdanske.com> - 2022-04-19 00:50 +0200
Re: backing up backups David Wright <deblis@lionunicorn.co.uk> - 2022-04-21 23:00 +0200
Re: backing up backups Keith Bainbridge <keithrboz@gmail.com> - 2022-04-19 06:00 +0200
Re: backing up backups David Wright <deblis@lionunicorn.co.uk> - 2022-04-19 18:10 +0200
csiph-web