linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Borut Rozman <borut.rozman@bioch.ox.ac.uk>
To: "linux-lvm@lists.linux.dev" <linux-lvm@lists.linux.dev>
Subject: Problems on enabling snapshots after reboot,.
Date: Wed, 25 Oct 2023 12:55:26 +0000	[thread overview]
Message-ID: <fa6f76d0422d63ce89ec7aea2ecfe3c7184f3696.camel@bioch.ox.ac.uk> (raw)

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.

Borut

             reply	other threads:[~2023-10-25 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 12:55 Borut Rozman [this message]
2023-10-26 11:42 ` Problems on enabling snapshots after reboot, Zdenek Kabelac

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=fa6f76d0422d63ce89ec7aea2ecfe3c7184f3696.camel@bioch.ox.ac.uk \
    --to=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).