From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: Borut Rozman <borut.rozman@bioch.ox.ac.uk>,
"linux-lvm@lists.linux.dev" <linux-lvm@lists.linux.dev>
Subject: Re: Problems on enabling snapshots after reboot,.
Date: Thu, 26 Oct 2023 13:42:35 +0200 [thread overview]
Message-ID: <bf108e22-0f19-44c3-90ad-dfed9eed683d@gmail.com> (raw)
In-Reply-To: <fa6f76d0422d63ce89ec7aea2ecfe3c7184f3696.camel@bioch.ox.ac.uk>
Dne 25. 10. 23 v 14:55 Borut Rozman napsal(a):
> Hi everyone,
>
> I have a machine where I run snapshots of the FS every 12 hours, and
> keep a week lot of those snapshots. After a crash or a clean restart,
> filesystem with snapshots does not get enabled and I have to wait
> several hours for lvm snapshots to get back online which of course is
> stressful. Last time I had to wait for 8 hours for all the snapshots to
> get enabled and then I had to remove all the snapshots so my FS would
> come up normally. I was wondering if this is a know issue or how can I
> avoid this.
>
> PS: FS is about 200TB in size and snapshots 5TB in size but they might
> be even empty.
>
Hi
Unfortunately you are misusing the original *thick* snapshot purpose.
It's been designed to be a short living small sized object.
If your snapshot gets into the GiB range - it gets very very inefficient.
You should check the thin-pool and its snapshot capabilities - where your
operation should be mostly instant then. And there is not a problem of
amplified write when you take a multiple snapshot of the same volume and you
can even take snapshot of a snapshot.
With 5TiB old thick snapshot there is simply a zero chance to fly.
Regards
Zdenek
prev parent reply other threads:[~2023-10-26 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 12:55 Problems on enabling snapshots after reboot, Borut Rozman
2023-10-26 11:42 ` Zdenek Kabelac [this message]
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=bf108e22-0f19-44c3-90ad-dfed9eed683d@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=borut.rozman@bioch.ox.ac.uk \
--cc=linux-lvm@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).