From: Chris Cox <chris_cox@stercomm.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm support
Date: Fri Dec 12 13:11:01 2003 [thread overview]
Message-ID: <3FDA1272.8050801@stercomm.com> (raw)
In-Reply-To: <9BBB7C9EFEF1874BAC4DC204E867EFAF02560D9E@s99mail06>
Little, Chris wrote:
> Is snapshot now unsupported? Or am I asking the wrong questions or
> directing to the wrong place. since it is an option to lvcreate and the
> maintainer lists sistina, i thought this would be the place to ask
> questions.
Can't speak for sistina... but I do agree with your
prior comments about it being buggy and unreliable.
In simple scenarios it seems to work ok... but
we had to use link-farm style solution instead
in order to make our disk based backup cache
work. Your (well I asuume you had this too) out
of memory condition can be somewhat handled I believe
with a larger memory initrd.... but it's a temporary
fixup at best.... we started running out
of memory again.. just took longer.
Running SUSE 8.2 with 6TB of disk backup area.
prev parent reply other threads:[~2003-12-12 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 11:13 [linux-lvm] lvm support Little, Chris
2003-12-12 13:11 ` Chris Cox [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=3FDA1272.8050801@stercomm.com \
--to=chris_cox@stercomm.com \
--cc=linux-lvm@sistina.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