From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] rc4 can't take snaphots of 0.9.1_beta7 lvs
Date: Tue, 09 Oct 2001 15:48:00 -0400 [thread overview]
Message-ID: <536570000.1002656880@tiny> (raw)
In-Reply-To: <20011009203031.B1034@btconnect.com>
On Tuesday, October 09, 2001 08:30:31 PM +0100 Joe Thornber
<thornber@btconnect.com> wrote:
>> Well, it worked in beta7
>
> did it ? It may not have segfaulted, but did you check the data
> really carefully ? After all it took a while for anyone to realise the
> problem existed.
Perhaps I just got really lucky when testing beta7 and didn't end up with
any unaligned lvs. Regardless, we should be able to make new snapshots of
those volumes now. I'm less worried about supporting existing unaligned
snapshots.
So, I'm trying some things, I'll either post patches or beg for help
later ;-)
-chris
prev parent reply other threads:[~2001-10-09 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 15:32 [linux-lvm] rc4 can't take snaphots of 0.9.1_beta7 lvs Chris Mason
2001-10-09 15:58 ` Joe Thornber
2001-10-09 16:30 ` Chris Mason
2001-10-09 19:30 ` Joe Thornber
2001-10-09 19:42 ` Joe Thornber
2001-10-09 20:01 ` Chris Mason
2001-10-09 19:48 ` Chris Mason [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=536570000.1002656880@tiny \
--to=mason@suse.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;
as well as URLs for NNTP newsgroup(s).