From: Ming Zhang <mingz@ele.uri.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Progress on LVM2 snapshots
Date: Thu, 28 Jul 2005 16:50:01 -0400 [thread overview]
Message-ID: <1122583801.9888.59.camel@localhost.localdomain> (raw)
In-Reply-To: <517d02700b97c3eb5b81085969ec0e28@redhat.com>
On Thu, 2005-07-28 at 15:45 -0500, Jonathan E Brassow wrote:
> On Jul 28, 2005, at 3:26 PM, Ming Zhang wrote:
>
> > Thanks a lot for this information.
> np
>
> > Is there anything external people like us can do to speed up this?
>
> 1) File detailed bug reports
> 2) complain on this list
> 3) submit patches
>
> > There
> > are many people waiting for this snapshot feature since it is so useful
> > and essential. frankly, i know there are plan to replace md with dm,
> > but
> > since md is already stable and this snapshot is very unstable, why not
> > do this first? :P
>
> The squeaky wheel gets the grease. Right now, multipath, [cluster]
> mirroring have been getting all the attention at the expense of single
> machine snap-shot. Hopefully, we can get snapshots soon.
>
:P u are rite. this is the truth. when both are important, loud voice
gains.
> brassow
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2005-07-28 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 11:45 [linux-lvm] Progress on LVM2 snapshots Mukund
2005-07-28 17:44 ` Ming Zhang
2005-07-28 20:06 ` Jonathan E Brassow
2005-07-28 20:26 ` Ming Zhang
2005-07-28 20:45 ` Jonathan E Brassow
2005-07-28 20:50 ` Ming Zhang [this message]
2005-07-29 20:47 ` Alasdair G Kergon
2005-07-29 21:13 ` Ming Zhang
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=1122583801.9888.59.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.