From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Suggestions for backup scheme?
Date: Fri, 9 Feb 2024 15:48:45 +0000 [thread overview]
Message-ID: <7b7a8788-b425-450e-b8b6-7ab98c7892dc@youngman.org.uk> (raw)
In-Reply-To: <4882577.GXAFRqVoOG@iris>
On 09/02/2024 12:57, J. Roeleveld wrote:
>> I don't understand it exactly, but what I think happens is when I create
>> the snapshot it allocates, let's say, 1GB. As I write to the master
>> copy, it fills up that 1GB with CoW blocks, and the original blocks are
>> handed over to the backup snapshot. And when that backup snapshot is
>> full of blocks that have been "overwritten" (or in reality replaced),
>> lvm just adds another 1GB or whatever I told it to.
> That works with a single snapshot.
> But, when I last used LVM like this, I would have multiple snapshots. When I
> change something on the LV, the original data would be copied to the snapshot.
> If I would have 2 snapshots for that LV, both would grow at the same time.
>
> Or is that changed in recent versions?
Has what changed? As I understand it, the whole point of LVM is that
everything is COW. So any individual block can belong to multiple snapshots.
When you write a block, the original block is not changed. A new block
is linked in to the current snapshot to replace the original. The
original block remains linked in to any other snapshots.
So disk usage basically grows by the number of blocks you write. Taking
a snapshot will use just a couple of blocks, no matter how large your LV is.
>
>> So when I delete a snapshot, it just goes through those few blocks,
>> decrements their use count (if they've been used in multiple snapshots),
>> and if the use count goes to zero they're handed back to the "empty" pool.
> I know this is how ZFS snapshots work. But am not convinced LVM snapshots work
> the same way.
>
>> All I have to do is make sure that the sum of my snapshots does not fill
>> the lv (logical volume). Which in my case is a raid-5.
> I assume you mean PV (Physical Volume)?
Quite possibly. VG, PV, LV. I know which one I need (by reading the
docs), I don't particularly remember which is which off the top of my head.
>
> I actually ditched the whole idea of raid-5 when drives got bigger than 1TB. I
> currently use Raid-6 (or specifically RaidZ2, which is the ZFS "equivalent")
>
Well, I run my raid over dm-integrity so, allegedly, I can't suffer disk
corruption. My only fear is a disk loss, which raid-5 will happily
recover from. And I'm not worried about a double failure - yes it could
happen, but ...
Given that my brother's ex-employer was quite happily running a raid-6
with maybe petabytes of data, over a double disk failure (until an
employee went into the data centre and said "what are those red
lights"), I don't think my 20TB of raid-5 is much :-)
Cheers,
Wol
next prev parent reply other threads:[~2024-02-09 15:48 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 18:15 [gentoo-user] Suggestions for backup scheme? Grant Edwards
2024-01-30 18:47 ` Thelma
2024-01-30 19:29 ` [gentoo-user] " Grant Edwards
2024-01-30 18:54 ` [gentoo-user] " Michael
2024-01-30 19:32 ` [gentoo-user] " Grant Edwards
2024-01-30 19:19 ` [gentoo-user] " Rich Freeman
2024-01-30 19:43 ` [gentoo-user] " Grant Edwards
2024-01-30 20:08 ` [gentoo-user] " Wol
2024-01-30 20:15 ` Rich Freeman
2024-01-30 20:38 ` [gentoo-user] " Grant Edwards
2024-01-31 8:14 ` gentoo-user
2024-01-31 11:45 ` John Covici
2024-01-31 13:01 ` Rich Freeman
2024-01-31 15:50 ` Grant Edwards
2024-01-31 17:40 ` Thelma
2024-01-31 17:56 ` Rich Freeman
2024-01-31 18:42 ` Wols Lists
2024-01-31 21:30 ` Rich Freeman
2024-02-01 10:16 ` Michael
2024-02-05 12:55 ` J. Roeleveld
2024-02-05 13:35 ` Rich Freeman
2024-02-06 13:12 ` J. Roeleveld
2024-02-06 20:27 ` Wols Lists
2024-02-07 11:11 ` J. Roeleveld
2024-02-07 21:59 ` Wols Lists
2024-02-08 6:32 ` J. Roeleveld
2024-02-08 17:36 ` Wols Lists
2024-02-09 12:53 ` J. Roeleveld
2024-02-06 15:38 ` Grant Edwards
2024-02-06 16:13 ` J. Roeleveld
2024-02-06 17:22 ` Grant Edwards
2024-02-07 11:21 ` J. Roeleveld
2024-01-31 18:00 ` Grant Edwards
2024-02-02 23:39 ` Grant Edwards
2024-02-02 23:58 ` Mark Knecht
2024-02-03 16:02 ` Grant Edwards
2024-02-03 17:05 ` Wol
2024-02-04 6:24 ` Grant Edwards
2024-02-04 9:59 ` Wols Lists
2024-02-04 15:48 ` Grant Edwards
2024-02-05 8:28 ` Wols Lists
2024-02-06 15:35 ` Grant Edwards
2024-02-06 16:19 ` J. Roeleveld
2024-02-06 17:29 ` Grant Edwards
2024-02-07 11:04 ` J. Roeleveld
2024-02-06 23:17 ` Wols Lists
2024-02-07 11:07 ` J. Roeleveld
2024-02-07 21:50 ` Wols Lists
2024-02-08 6:38 ` J. Roeleveld
2024-02-08 17:44 ` Wols Lists
2024-02-09 12:57 ` J. Roeleveld
2024-02-09 15:48 ` Wols Lists [this message]
2024-02-09 17:11 ` Peter Humphrey
2024-02-06 20:49 ` Wols Lists
2024-02-03 13:02 ` Michael
2024-02-03 16:15 ` Grant Edwards
2024-02-03 17:32 ` Rich Freeman
2024-02-03 18:10 ` Michael
2024-02-05 12:48 ` J. Roeleveld
2024-01-31 15:38 ` Grant Edwards
2024-02-04 10:54 ` [gentoo-user] " Paul Ezvan
2024-02-07 22:36 ` Frank Steinmetzger
2024-02-08 5:26 ` William Kenworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b7a8788-b425-450e-b8b6-7ab98c7892dc@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox