From: Jon Bendtsen <jon+lvm@silicide.dk>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Snapshot resizing bug (LVM1)
Date: Thu Feb 6 06:03:01 2003 [thread overview]
Message-ID: <3E424EDF.CC7A4F56@silicide.dk> (raw)
In-Reply-To: 20030206112752.B22450@sistina.com
"Heinz J . Mauelshagen" wrote:
>
> Dale,
>
> thanks for finding this bug.
yeah, thanks from me too, i plan to TEST it.
> Obviously people don't resize populated snapshots very often or we'ld
> seen this one much earlier ;)
thats not true. I tried to resize polulated snapshots quite often, like
several times a day, but i gave up on that because it didnt work. Being
production machines they need to be stable.
So, why didnt i report the bug well... i didnt feel i had the time to
play arround with our production machines, and i have nowhere to test
it, so i just stopped doing snapshots. But i did email this mailing list
and described the usage and the errors i got. Not a patch no, but i feel
it was reported arround the end of october where i ran into it. Possibly
someone else did it before me.
See these links for more info:
http://lists.sistina.com/pipermail/linux-lvm/2002-October/012602.html
Okay, maybe i wasnt clear on reporting that problems continued after
downgrading, sorry about that.
http://lists.sistina.com/pipermail/linux-lvm/2002-October/012631.html
\x03
Not trying to sound negative and all it's great that this bug is gone,
but i feel that the effects of this bug was seen before. Maybe what is
needed is a better way to see what is bugs and what is
missconfiguration.
JonB
next prev parent reply other threads:[~2003-02-06 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 12:08 [linux-lvm] Snapshot resizing bug (LVM1) Dale J. Stephenson
2003-02-06 4:31 ` Heinz J . Mauelshagen
2003-02-06 6:03 ` Jon Bendtsen [this message]
2003-02-06 12:45 ` Heinz J . Mauelshagen
2003-02-12 13:27 ` Debian User
2003-02-13 6:15 ` Heinz J . Mauelshagen
2003-02-13 17:16 ` Heinz J . Mauelshagen
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=3E424EDF.CC7A4F56@silicide.dk \
--to=jon+lvm@silicide.dk \
--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