From: Tracy R Reed <treed@copilotconsulting.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Kernel oops
Date: Mon Sep 15 06:49:03 2003 [thread overview]
Message-ID: <20030915030139.A11888@copilotconsulting.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
Linux home 2.4.20 #18 SMP Fri Sep 12 22:49:21 PDT 2003 i686 GNU/Linux
home:~# lvcreate --version
LVM version: 1.95.15 (2003-01-10)
Library version: 0.96.07-ioctl-cvs (2002-11-21)
Driver version: 1.0.8
I created a script to take daily snapshots of my four logical volumes for
backup purposes. Approximately every other time I run it the whole lvm
system seems to freeze up. The first time it did this it crashed the whole
computer by not allowing any writes to disk. The second two times the
system didn't crash but I now have hung lvremove and lvcreate processes
which appear to require a reboot to clear. strace on the processes shows
nothing happening and kill -9 has no effect. In the dmesg I have lots of
"invalidate: busy buffer" and then a kernel oops:
Unable to handle kernel NULL pointer dereference at virtual address
00000001
printing eip:
ce6a16d0
*pde = 00000000
Oops: 0002
CPU: 1
EIP: 0010:[<ce6a16d0>] Tainted: P
EFLAGS: 00010202
eax: ce6a16d0 ebx: ce6a16a0 ecx: 00000010 edx: ce6a16d0
esi: 00000001 edi: 00000000 ebp: c023c230 esp: df6c3f3c
ds: 0018 es: 0018 ss: 0018
Process kcopyd (pid: 69, stackpage=df6c3000)
Stack: c023b83a ce6a16d0 00000001 00000001 00000b76 00000000 0000001b
00000000
c7cc3c10 cda29004 00000010 c023a52f d41f3e8c c7c7b218 c023a4e0
c7c7b218
c023c891 00000000 c7c7b218 cda29004 c031f858 c023c240 cda29004
c023c394
Call Trace: [<c023b83a>] [<c023a52f>] [<c023a4e0>] [<c023c891>]
[<c023c240>]
[<c023c394>] [<c023c424>] [<c023c230>] [<c023c535>] [<c01075ee>]
[<c023c480>]
Code: d0 16 6a ce d0 16 6a ce 00 00 00 00 69 dd 63 00 8c ff 7c f9
This seems to be a reproduceable problem. I was under the impression that
LVM was fairly stable by this point. The first crash happened in the
middle of a backup that had been running for 48 hours which I will now
have to restart. Not too happy. :( Uh oh...now the system can't write to
disk again and I will have to reboot.
--
Tracy Reed
http://copilotconsulting.com
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2003-09-15 6:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 6:49 Tracy R Reed [this message]
2003-09-16 4:50 ` [linux-lvm] FYI: Going back to LVM1 from LVM2 Rickard Olsson
2003-09-16 8:25 ` AJ Lewis
2003-09-18 8:09 ` Rickard Olsson
2003-09-16 13:19 ` [linux-lvm] Kernel oops Tracy R Reed
2003-09-23 23:14 ` [linux-lvm] remove Gene
-- strict thread matches above, loose matches on Subject: below --
2001-08-01 21:24 [linux-lvm] Kernel Oops Frode Tennebø
1999-11-29 17:19 [linux-lvm] kernel oops Rusty Wickell
1999-11-30 0:00 ` Heinz Mauelshagen
1999-11-23 16:47 Rusty Wickell
1999-11-19 21:35 Rusty Wickell
1999-11-19 22:58 ` Matthias G. Eckermann
1999-11-20 14:22 ` Sune Kirkeby
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=20030915030139.A11888@copilotconsulting.com \
--to=treed@copilotconsulting.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.