From: Alex Owen <rao3@leicester.ac.uk>
To: linux-lvm@redhat.com
Subject: [linux-lvm] (no subject)
Date: Fri, 18 Jun 2004 17:33:00 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.58.0406181723320.4709@pc167.cc.le.ac.uk> (raw)
Hello,
This morning I had an oops which I think is due to extending a
LVM1 LVsnapshot.
I'm running a custom compiled 2.4.26 kernel. Debian source + LVM1.0.8 +
VFS-Lock from dm tarball.
If anyone can give me any pointers to informantion of debuging such
problems that would be great!
Thanks in advance for any advice on debugging.
Here is the syslog output:
Jun 18 07:39:02 falcon /USR/SBIN/CRON[3094]: (root) CMD ([ -x /usr/local/sbin/cron.snapshotextend ] && /usr/local/sbin/cron.snapshotextend)
Jun 18 07:39:03 falcon kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Jun 18 07:39:03 falcon kernel: printing eip:
Jun 18 07:39:03 falcon kernel: f8855b17
Jun 18 07:39:03 falcon kernel: *pde = 1236b001
Jun 18 07:39:03 falcon kernel: *pte = 00000000
Jun 18 07:39:03 falcon kernel: Oops: 0000
Jun 18 07:39:03 falcon kernel: CPU: 3
Jun 18 07:39:03 falcon kernel: EIP: 0010:[ide-cd:__insmod_ide-cd_O/lib/modules/2.4.26-686-smp-lvm-vfslock/ke+-2135273/96] Tainted: P
Jun 18 07:39:03 falcon kernel: EFLAGS: 00010202
Jun 18 07:39:03 falcon kernel: eax: 00000000 ebx: f8ac3260 ecx: 00000000 edx: 00000000
Jun 18 07:39:03 falcon kernel: esi: 00402400 edi: f724aa00 ebp: 00006804 esp: c43d7dd0
Jun 18 07:39:03 falcon kernel: ds: 0018 es: 0018 ss: 0018
Jun 18 07:39:03 falcon kernel: Process kupdated (pid: 9, stackpage=c43d7000)
Jun 18 07:39:03 falcon kernel: Stack: f724aa00 f724ab70 f7c92970 00200000 00000080 00000002 00000000 00000000
Jun 18 07:39:03 falcon kernel: f88526d1 c43d7e2e c43d7e30 00402380 f724aa00 00003a02 eda084a0 00000080
Jun 18 07:39:03 falcon kernel: 00200000 c7d80f80 000c00b0 f7c92800 f7c89000 00402380 00000000 68040000
Jun 18 07:39:03 falcon kernel: Call Trace: [ide-cd:__insmod_ide-cd_O/lib/modules/2.4.26-686-smp-lvm-vfslock/ke+-2148655/96]
[ide-cd:__insmod_ide-cd_O/lib/modules/2.4.26-686-smp-lvm-vfslock/ke+-2148425/96] [generic_make_request+288/304] [submit_bh+86/224]
[write_locked_buffers+32/44]
Jun 18 07:39:03 falcon kernel: [write_some_buffers+278/364] [sync_old_buffers+101/168] [kupdate+329/384] [ret_from_fork+6/32] [kupdate+0/384]
[arch_kernel_thread+40/56]
Jun 18 07:39:03 falcon kernel:
Jun 18 07:39:03 falcon kernel: Code: 8b 01 39 d9 74 37 39 71 08 75 ef 66 39 69 0c 75 e9 83 7c 24
The cron job I suspect of trigering the kernel bug is
/usr/local/sbin/cron.snapshotextend :
---8<---
#!/bin/bash
#################################################
# script to extend snapshots before they fill up!
#################################################
#for lv in /dev/vg00/SNAP* ; do
for lv in $( ls /dev/vg00/SNAP* 2>/dev/null ) ; do
/sbin/lvdisplay $lv | grep "Allocated to snapshot" | \
( read junk junk junk LVpercent LVvalues
#make integer percentage
LVpercent=${LVpercent%\%}
LVpercent=${LVpercent%.*}
#get usage and size from values
LVusage=${LVvalues%%/*]}
LVusage=${LVusage#[}
LVsize=${LVvalues##[*/}
LVsize=${LVsize%]}
#echo lv $lv
#echo percent $LVpercent
#echo used $LVusage
#echo size $LVsize
if /usr/bin/expr $LVpercent '>=' 80 >/dev/null ; then
LVsizeunit=${LVsize##* }
LVsizeunit=${LVsizeunit%B}
#calc 20% of existing snapshot size
LVextension=${LVsize%% *}
LVextension=${LVextension%.*}
LVextension=$(( $LVextension * 20 / 100 ))
echo /sbin/lvextend -L+$LVextension$LVsizeunit $lv
/sbin/lvextend -L+${LVextension}${LVsizeunit} $lv
echo DONE
fi
)
done
---8<---
----------------------------------------------------------------
Dr Richard Alexander Owen Unix System Administrator
The Computer Centre E-mail: rao3@le.ac.uk
University of Leicester Tel: (0116) 2525133
University Road Fax: (0116) 2525027
Leicester LE1 7RH
----------------------------------------------------------------
next reply other threads:[~2004-06-18 16:33 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 16:33 Alex Owen [this message]
2004-06-20 8:46 ` [linux-lvm] (no subject) Heinz Mauelshagen
2004-06-21 10:31 ` [linux-lvm] Re: Snapshot related Oops? - Was:(no subject) Alex Owen
-- strict thread matches above, loose matches on Subject: below --
2010-02-03 15:15 [linux-lvm] (no subject) Nicholas Robinson
2009-06-28 22:31 [linux-lvm] Testmail to see if my other two mails are too big for the MTA Daniel Mierswa
2009-06-28 22:32 ` [linux-lvm] (no subject) Piete Brooks
2007-09-13 13:11 Dony Pierre
2007-01-17 12:29 antonio_cecere
2006-03-16 15:08 fredrik.backman
2006-03-16 17:53 ` Luca Berra
2005-08-23 8:13 fredrik.backman
2005-07-14 7:53 fredrik.backman
2005-07-14 13:50 ` AJ Lewis
2005-07-03 18:56 Jean-Luc Coulon (f5ibh)
2005-07-03 22:09 ` Luca Berra
2005-06-14 1:39 gary chen
2004-06-08 17:59 Jerry Hardwick
2004-06-08 18:18 ` Garrick Staples
2004-06-08 18:23 ` Jan-Benedict Glaw
2004-06-09 12:53 ` David Greaves
2004-04-22 19:30 Tomas
2004-02-23 12:41 markw
2004-02-18 9:33 christophe.varoqui
2004-02-02 4:51 Martins Pukitis
2004-02-11 17:07 ` Heinz Mauelshagen
2004-02-13 9:10 ` Martins Pukitis
2003-12-01 19:19 Jens A. Tkotz
2003-10-27 19:28 Victor Tan
2003-06-29 11:10 Howard Clifford
2003-06-30 9:51 ` Patrick Caulfield
2003-06-30 9:51 ` Heinz J . Mauelshagen
[not found] <MichaelVogt@abcsystems.ch>
2003-05-02 3:51 ` Michael Vogt
2003-05-10 8:37 ` Ewen McNeill
2002-12-04 20:04 Ì·ÞÈÈð
2002-12-05 17:05 ` Heinz J . Mauelshagen
2002-12-02 4:02 Nirmala S
2002-12-03 7:34 ` Patrick Caulfield
2002-12-03 7:34 ` Heinz J . Mauelshagen
2002-10-03 4:49 Ruchika Adukia
2002-10-07 7:27 ` Heinz J . Mauelshagen
2002-09-27 2:52 Shuvodeep Ghosh
2002-09-27 7:20 ` Heinz J . Mauelshagen
2002-09-24 14:53 Rob Schwartz
2002-09-27 7:19 ` Heinz J . Mauelshagen
2002-07-27 1:03 Amit Agrawal, Noida
2002-05-22 7:03 lysindybear
2002-05-22 7:20 ` Joe Thornber
2002-02-15 6:30 IDanz91278
2002-01-16 20:25 Sil Lee
2002-01-17 5:51 ` Heinz J . Mauelshagen
2002-01-17 5:51 ` Patrick Caulfield
2002-01-17 8:18 ` Heinz J . Mauelshagen
2002-01-17 9:20 ` Patrick Caulfield
2002-01-17 11:05 ` Heinz J . Mauelshagen
2002-01-17 11:22 ` Patrick Caulfield
2002-01-18 4:31 ` Heinz J . Mauelshagen
2002-01-17 7:02 ` Chris Danis
2002-01-14 9:12 Stefan Huber
2002-01-14 9:32 ` Adrian Phillips
2002-01-15 1:31 ` Stefan Huber
2002-01-15 1:38 ` Adrian Phillips
2002-01-15 1:51 ` Stefan Huber
2001-11-11 13:08 paco
2001-10-30 14:01 Tren Blackburn
2001-09-24 17:31 www.simpsonsworld.de
2001-08-23 17:27 Peter A. Borovcnik
2001-05-08 17:57 Diehl, Jeffrey
2001-05-08 19:15 ` AJ Lewis
2001-05-03 0:48 [linux-lvm] LVM Questions Darren Young
2001-05-03 1:45 ` Evan Day
2001-05-03 6:56 ` Adrian Phillips
2001-05-04 9:33 ` Heinz J. Mauelshagen
2001-05-04 7:45 ` Adrian Phillips
2001-05-04 10:38 ` Heinz J. Mauelshagen
2001-05-04 9:38 ` Adrian Phillips
2001-05-04 13:39 ` Heinz J. Mauelshagen
2001-05-08 7:38 ` [linux-lvm] (no subject) Merence Sibomana
2001-05-01 10:36 Heinz J. Mauelshagen
2001-04-04 16:36 Sergey Berkovich
2001-04-04 17:45 ` Heinz J. Mauelshagen
2001-02-28 18:36 bertrand.sirodot
2001-02-28 21:44 ` AJ Lewis
2001-02-11 19:16 Pete lamb
2001-02-11 19:46 ` Steven Lembark
2001-02-11 20:03 ` Pete lamb
2001-02-12 20:40 ` Andreas Dilger
2001-01-09 0:22 Gordon Schumacher
2000-12-19 2:43 Brad Corsello
1999-06-11 13:17 Paul Hofman
1999-05-26 15:28 Chris Zimmerman
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=Pine.LNX.4.58.0406181723320.4709@pc167.cc.le.ac.uk \
--to=rao3@leicester.ac.uk \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).