linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@lists.linux.dev
Subject: Re: Best use of a small SSD with LVM
Date: Thu, 07 Aug 2025 02:58:40 -0400	[thread overview]
Message-ID: <a643ce5c6f334b595169a65ac754e22aaf025f99.camel@interlinx.bc.ca> (raw)
In-Reply-To: <d754fa089d273.c3f10ab0005ac8@gmail.com>

But is death of an SSD for a write-through cache all that catastrophic?

The underlying data (on the spinning rust drives) is still there and
coherent and recovery is simply removing the reference to the cache,
(i.e. changing your mount devices, etc.) no?

Cheers,
b.

  parent reply	other threads:[~2025-08-07  6:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 22:35 Best use of a small SSD with LVM Brian J. Murrell
2025-08-07  2:22 ` matthew patton
2025-08-07  5:59   ` Brian J. Murrell
     [not found]   ` <d754fa089d273.c3f10ab0005ac8@gmail.com>
2025-08-07  6:58     ` Brian J. Murrell [this message]
2025-08-07 15:21   ` John Stoffel
2025-08-07 17:45     ` Brian J. Murrell
2025-08-07 15:16 ` John Stoffel

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=a643ce5c6f334b595169a65ac754e22aaf025f99.camel@interlinx.bc.ca \
    --to=brian@interlinx.bc.ca \
    --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).