From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] kernel BUG at dm-snapshot.c:986!
Date: Tue May 20 02:46:02 2003 [thread overview]
Message-ID: <20030520093717.D9086@sistina.com> (raw)
In-Reply-To: <1481523360.1053068601@[192.168.23.5]>; from max@lsit.ucsb.edu on Fri, May 16, 2003 at 07:03:21AM -0700
On Fri, May 16, 2003 at 07:03:21AM -0700, Max Kalika wrote:
> Quoting "Heinz J . Mauelshagen" <mauelshagen@sistina.com>:
> >
> > that code has changed recently. Have you tried if public device-mapper
> > cvs fixes it?
> >
> > Keep in mind, that code is under construction there!
>
> Heinz,
>
> Thank you for your reply. Could you provide a pointer or to as to how to
> try the CVS device-mapper? I just checked out the tree and the patches
> look the same as those that are in the release tarball (0.96.08).
Sorry, I assumed you had an older content.
> I'm
> assuming I have to do something with the dm-ioctl.[ch] files found under
> the kernel directory in the device-mapper CVS tree as that is where I
> noticed a lot of activity last month. Do I just copy these manually into
> my kernel tree or is there something else that needs to be done as well?
> (Or do you know if there will be a new set of kernel patches cut soon?)
They'll be released with LVM 2.0 ASAP (delayed by a bug fix).
> Thank you for your time and patience.
>
> --
> ---max kalika
> --max@lsit.ucsb.edu
> -lsit systems administrator
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2003-05-20 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 7:34 [linux-lvm] kernel BUG at dm-snapshot.c:986! Max Kalika
2003-05-16 6:16 ` Heinz J . Mauelshagen
2003-05-16 9:01 ` Max Kalika
2003-05-20 2:46 ` Heinz J . Mauelshagen [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=20030520093717.D9086@sistina.com \
--to=mauelshagen@sistina.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 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.