[HN Gopher] Imaging mounted disk volumes under duress (2021)
___________________________________________________________________
Imaging mounted disk volumes under duress (2021)
Author : yamrzou
Score : 41 points
Date : 2025-01-12 12:41 UTC (3 days ago)
(HTM) web link (blog.benjojo.co.uk)
(TXT) w3m dump (blog.benjojo.co.uk)
| nyrikki wrote:
| FYI, while these block level methods do have a use case, parallel
| rsync and other file level tools are far safer and often faster
| with less additional load on the disk.
|
| Duplicating the OS/FS behavior hits the decidable problem and you
| just hope for the best with block level, often you won't notice
| corruption either.
| groby_b wrote:
| 1) The article's use case is _explicitly_ bootable images.
|
| 2) No, most of us don't "hope for the best" with imaging, but
| would like to actually achieve a reasonable level of
| confidence. If your approach to data integrity is "you probably
| won't notice corruption", you don't have an approach to data
| integrity.
| dambi0 wrote:
| 1) The article stated that using bootable images for backup
| was a preference. That doesn't invalidate asking whether
| that's an ideal preference
|
| 2) Arguing that it might be better to avoid such methods
| because of possible problems with data integrity isn't a lack
| of an approach to data integrity.
| thesnide wrote:
| I'm also doing bootable images. But the old way with a r/o
| initrd, that does then mount the rootfs.
|
| The rootfs can be mkfs and rsynced nicely.
|
| That said, the article is awesome and the idea very clever.
|
| But more to do streaming replication that dd catchup.
| Joel_Mckay wrote:
| initrd with native OverlayFS kernel support is very
| versatile. ;)
|
| Yet the btrfs, CephFS, or ZFS all have snapshot syncing
| tricks that make state mirrors far more practical and safe
| to pull off. =3
___________________________________________________________________
(page generated 2025-01-15 23:00 UTC)