From: Christophe Saout <christophe@saout.de>
To: Roger Gammans <roger@computer-surgery.co.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.18] oops in lvm or raid
Date: Mon, 29 Dec 2003 18:16:10 +0100 [thread overview]
Message-ID: <1072718170.5152.130.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <20031229145936.GA19936@computer-surgery.co.uk>
Am Mo, den 29.12.2003 schrieb Roger Gammans um 15:59:
> Dec 29 13:15:23 turin kernel: lvm -- giving up to snapshot /dev/rootvg/data_root on /dev/rootvg/data_20031218: out of spa
> Dec 29 13:15:23 turin kernel: Unable to handle kernel paging request at virtual address 00015618
> Dec 29 13:15:23 turin kernel: printing eip:
> Dec 29 13:15:23 turin kernel: c4847a7c
> c4847a7c -> lvm_snapshot_remap_block (c4847a0c)
>
> This is a stock kernel (bf2.4) from debian stable (Version: 2.4.18-5)
LVM1 snapshotting in the plain 2.4.18 kernel is known to have bugs.
You should upgrade to the latest LVM 1.0.8 kernel code. Well, I can't
access the Sistina website at the moment. I'm sure you can find a
lvm_1.0.8.tar.gz (or lvm_1.0.7.tar.gz which also has most bugs fixed)
somewhere.
In the directory LVM/1.0.8/kernel are some files:
Copy lvm.h to /usr/src/linux/include/linux and the rest to
/usr/src/linux/drivers/md (overwrite the old ones) and recompile the
kernel.
Or you can upgrade to the 2.4.23 kernel, I think it contains the LVM
1.0.7 code.
--
Christophe Saout <christophe@saout.de>
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
next prev parent reply other threads:[~2003-12-29 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 14:59 Roger Gammans
2003-12-29 17:16 ` Christophe Saout [this message]
2003-12-30 12:02 ` Roger Gammans
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=1072718170.5152.130.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roger@computer-surgery.co.uk \
/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
all inboxes | Powered by JetHome®