From: AJ Lewis <lewis@sistina.com>
To: Ed Tomlinson <tomlins@cam.org>
Subject: Re: [linux-lvm] [BUG] segmentation fault on snapshot with beta8
Date: Mon, 30 Jul 2001 08:35:50 -0500 [thread overview]
Message-ID: <20010730083550.A20819@sistina.com> (raw)
In-Reply-To: <20010727162747.9542515354@oscar.casa.dyndns.org>; from tomlins@cam.org on Fri, Jul 27, 2001 at 12:27:47PM -0400
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Fri, Jul 27, 2001 at 12:27:47PM -0400, Ed Tomlinson wrote:
> My impression with the above bug is that the snapshot is filling much too quickly
> and getting disabled. At this point seg faults start happening.
I saw some Oopses and segfaults on 2.4.6 on Friday, but after I put the kdb
into the kernel I can't reproduce it. I never see this with 2.4.7.
This was with LVM 0.9.1 Beta8 and the patches you previously mentioned.
--
AJ Lewis
Sistina Software Inc. Voice: 612-638-0500
1313 5th St SE, Suite 111 Fax: 612-638-0500
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
(Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
-----Begin Obligatory Humorous Quote----------------------------------------
File not found. Should I fake it? (Y/N)
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-07-30 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 12:27 [linux-lvm] [BUG] segmentation fault on snapshot with beta8 Ed Tomlinson
2001-07-27 15:21 ` AJ Lewis
2001-07-27 16:27 ` Ed Tomlinson
2001-07-30 13:35 ` AJ Lewis [this message]
2001-07-31 21:09 ` Ed Tomlinson
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=20010730083550.A20819@sistina.com \
--to=lewis@sistina.com \
--cc=linux-lvm@sistina.com \
--cc=tomlins@cam.org \
/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