From: Wallace Wadge <wwadge@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm + raid (confused)
Date: Wed, 30 Nov 2005 08:01:20 +0100 [thread overview]
Message-ID: <efef33d20511292301s1fe5cf0dp90180833f51e2360@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
Hi,
I've got a hardware raid in place. I'd like to add snapshots via lvm to it
but unfortunately the underlying filesystem is ext3 which cannot be resized
downwards; therefore I would like to add another disk.
Now for the problem:
I would like to add a secondary (physical) disk to the mix and use it for
snapshots only. However I do not want the lvm to stay writing to that disk
for normal data since this seconday disk would not be part of my hardware
raid. In other words, I wouldn't care if the snapshot drive failed because I
would just replace it.
Is this at all possible?
Thanks.
Wallace
[-- Attachment #2: Type: text/html, Size: 647 bytes --]
next reply other threads:[~2005-11-30 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 7:01 Wallace Wadge [this message]
2005-11-30 8:48 ` [linux-lvm] lvm + raid (confused) Heinz Mauelshagen
2005-11-30 9:08 ` [linux-lvm] " Wallace Wadge
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=efef33d20511292301s1fe5cf0dp90180833f51e2360@mail.gmail.com \
--to=wwadge@gmail.com \
--cc=linux-lvm@redhat.com \
/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).