* [Fwd: Bug#495949: grub-common: grub-probe segfaults]
[not found] ` <1219339864.4090.58.camel@fz.local>
@ 2008-08-21 18:05 ` Felix Zielcke
2008-08-24 10:05 ` Felix Zielcke
2008-08-27 9:40 ` Felix Zielcke
0 siblings, 2 replies; 3+ messages in thread
From: Felix Zielcke @ 2008-08-21 18:05 UTC (permalink / raw)
To: The development of GRUB 2; +Cc: jean-luc.coulon
[-- Attachment #1.1: Type: text/plain, Size: 2397 bytes --]
The report is on http://bugs.debian.org/495949
There seems to be some LVM/RAID related memory corruption somewhere.
On the report there's a backtrace, full backtrace and core file +
grub-probe binary attached.
This doestn't make any sense to me, so I hope some of you else has one.
On Debian BTS we have a wishlist report for encrypted LVM but that
person isn't saying at all that grub-probe segfaults
http://bugs.debian.org/463107
-------- Weitergeleitete Nachricht --------
> Von: Jean-Luc Coulon (f5ibh) <jean-luc.coulon@wanadoo.fr>
> Antwort an: Jean-Luc Coulon (f5ibh) <jean-luc.coulon@wanadoo.fr>,
> 495949@bugs.debian.org
> An: 495949@bugs.debian.org
> Kopie: grub-devel@gnu.org
> Betreff: Bug#495949: grub-common: grub-probe segfaults
> Datum: Thu, 21 Aug 2008 19:44:49 +0200
>
> Le 21.08.2008 19:31:04, Felix Zielcke a écrit :
> >
> >Am Donnerstag, den 21.08.2008, 19:12 +0200 schrieb Jean-Luc Coulon
> >(f5ibh):
> >>
> >> So, attached the bt full output and the grub-probe binary (bzip2,
> >> warning, it is built for X86_64).
> >That's what I'm using too
> >I have now even compiled myself the 24-8 and used that grub-probe
> >binary
> >with your core file.
> >I haven't thought that this would work.
> >
> >It's very weird, I really don't understand the backtrace.
> >It looks like really severe memory corruption.
> >
> >Seems like it has something to do with your LVM or RAID
> >so maybe output of:
> >lvdisplay
> >vgdisplay
> >pvdisplay
> >mdadm -Q --detail /dev/md0
> >mdadm -Q --detail /dev/md1
> >mdadm -Q --detail /dev/md2
>
> Ok.
> Attached the output of each command.
> (/dev/md2 is encrypted with luks).
>
>
> >
> >helps.
> >
> >> Remark, I subscribe grub-devel list but my message was rejeted :-o
> >
> >The list mail erver has unfortunately sometimes problems, I noticed
> >this
> >myself :(
> >
> >would be very nice of you if you send another mail to grub-devel
> after
> >you made sure you get the `welcome to grub-devel' mail,
> >else I just forward it but I think it's better to have the discussion
> >with you :)
> >And on grub-devel there's not only Robert and me but the others too.
>
> J-L
> _______________________________________________
> Pkg-grub-devel mailing list
> Pkg-grub-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
[-- Attachment #1.2: lvdisplay.txt --]
[-- Type: text/plain, Size: 5961 bytes --]
--- Logical volume ---
LV Name /dev/cryptvg0/opt_lv
VG Name cryptvg0
LV UUID opnuev-fu0Z-pW1K-8qMB-vZnY-KCPx-juG5zQ
LV Write Access read/write
LV Status available
# open 1
LV Size 3.17 GB
Current LE 812
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5
--- Logical volume ---
LV Name /dev/cryptvg0/local_lv
VG Name cryptvg0
LV UUID cWKbtN-KTTr-kTiv-wZUs-y5oE-svJ1-FNy6E0
LV Write Access read/write
LV Status available
# open 1
LV Size 3.88 GB
Current LE 993
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6
--- Logical volume ---
LV Name /dev/cryptvg0/tmp_lv
VG Name cryptvg0
LV UUID jfBWUN-97E3-7430-QXv5-rzqe-CKFj-Fucqa6
LV Write Access read/write
LV Status available
# open 1
LV Size 6.00 GB
Current LE 1536
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:7
--- Logical volume ---
LV Name /dev/cryptvg0/photos_lv
VG Name cryptvg0
LV UUID syYrHg-zvse-wRkr-9ae5-PoCG-0cl8-KNhyXY
LV Write Access read/write
LV Status available
# open 1
LV Size 11.50 GB
Current LE 2944
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:8
--- Logical volume ---
LV Name /dev/cryptvg0/music_lv
VG Name cryptvg0
LV UUID 5C3fYQ-5Snq-dM2Q-L4nX-Obkb-ZI1B-2lTIDE
LV Write Access read/write
LV Status available
# open 1
LV Size 3.15 GB
Current LE 806
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:9
--- Logical volume ---
LV Name /dev/cryptvg0/iso_lv
VG Name cryptvg0
LV UUID QIQ1r4-FqEL-at2b-qeZo-Fik0-939G-g4cJuh
LV Write Access read/write
LV Status available
# open 0
LV Size 5.00 GB
Current LE 1280
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:10
--- Logical volume ---
LV Name /dev/cryptvg0/mail_lv
VG Name cryptvg0
LV UUID nXn8gJ-v4zn-qQi5-xLFc-znav-q6uS-hfJur9
LV Write Access read/write
LV Status available
# open 1
LV Size 1.00 GB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:11
--- Logical volume ---
LV Name /dev/cryptvg0/home_lv
VG Name cryptvg0
LV UUID koR32q-Wi3i-TrMB-nufP-Bcc8-acx2-3AtfaO
LV Write Access read/write
LV Status available
# open 1
LV Size 4.68 GB
Current LE 1199
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:12
--- Logical volume ---
LV Name /dev/vg0/root_lv
VG Name vg0
LV UUID gLtaR8-JajG-PZCu-izsz-e8dJ-yeS4-sZtXPB
LV Write Access read/write
LV Status available
# open 1
LV Size 500.00 MB
Current LE 125
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Name /dev/vg0/var_lv
VG Name vg0
LV UUID 9YpHqM-aaX7-SD4W-e7Ip-xYt4-pN1B-sYMG2L
LV Write Access read/write
LV Status available
# open 1
LV Size 1.20 GB
Current LE 306
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Name /dev/vg0/usr_lv
VG Name vg0
LV UUID TBfCp3-uGAO-monA-4oUP-co90-DD4G-5tOH2g
LV Write Access read/write
LV Status available
# open 1
LV Size 8.70 GB
Current LE 2228
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
--- Logical volume ---
LV Name /dev/vg0/swap_lv
VG Name vg0
LV UUID EzuVCV-PaaZ-eceW-rP16-0iF3-97IY-Bs2FEe
LV Write Access read/write
LV Status available
# open 1
LV Size 8.00 GB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
[-- Attachment #1.3: pvdisplay.txt --]
[-- Type: text/plain, Size: 737 bytes --]
--- Physical volume ---
PV Name /dev/dm-4
VG Name cryptvg0
PV Size 46.37 GB / not usable 4.06 MB
Allocatable yes
PE Size (KByte) 4096
Total PE 11869
Free PE 2043
Allocated PE 9826
PV UUID RWHGoZ-Qjsq-Bfcf-uCzz-R5zq-2ODV-kv3cKW
--- Physical volume ---
PV Name /dev/md1
VG Name vg0
PV Size 27.94 GB / not usable 3.81 MB
Allocatable yes
PE Size (KByte) 4096
Total PE 7151
Free PE 2444
Allocated PE 4707
PV UUID JJFpnM-UkCM-uN2O-rm83-KChj-KJAk-vnxZk9
[-- Attachment #1.4: vgdisplay.txt --]
[-- Type: text/plain, Size: 1298 bytes --]
--- Volume group ---
VG Name cryptvg0
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 212
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 8
Open LV 7
Max PV 0
Cur PV 1
Act PV 1
VG Size 46.36 GB
PE Size 4.00 MB
Total PE 11869
Alloc PE / Size 9826 / 38.38 GB
Free PE / Size 2043 / 7.98 GB
VG UUID HicUsY-vNNC-zDYM-ADGj-slCx-9fEB-w1rCjX
--- Volume group ---
VG Name vg0
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 166
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 4
Open LV 4
Max PV 0
Cur PV 1
Act PV 1
VG Size 27.93 GB
PE Size 4.00 MB
Total PE 7151
Alloc PE / Size 4707 / 18.39 GB
Free PE / Size 2444 / 9.55 GB
VG UUID mRNAoJ-8alV-bRIA-wBt2-yow0-AIei-DqBalg
[-- Attachment #1.5: md0.txt --]
[-- Type: text/plain, Size: 728 bytes --]
/dev/md0:
Version : 00.90
Creation Time : Sun Feb 17 17:50:51 2008
Raid Level : raid1
Array Size : 232832 (227.41 MiB 238.42 MB)
Used Dev Size : 232832 (227.41 MiB 238.42 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Thu Aug 21 19:40:36 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 19628d78:d50fb284:cc328929:8db8e0da
Events : 0.198
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 active sync /dev/sdc1
[-- Attachment #1.6: md1.txt --]
[-- Type: text/plain, Size: 729 bytes --]
/dev/md1:
Version : 00.90
Creation Time : Sun Feb 17 17:50:58 2008
Raid Level : raid1
Array Size : 29294400 (27.94 GiB 30.00 GB)
Used Dev Size : 29294400 (27.94 GiB 30.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Thu Aug 21 19:40:50 2008
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 0910e15f:d2012447:cc328929:8db8e0da
Events : 0.105
Number Major Minor RaidDevice State
0 8 18 0 active sync /dev/sdb2
1 8 34 1 active sync /dev/sdc2
[-- Attachment #1.7: md2.txt --]
[-- Type: text/plain, Size: 727 bytes --]
/dev/md2:
Version : 00.90
Creation Time : Sun Feb 17 17:51:03 2008
Raid Level : raid1
Array Size : 48620608 (46.37 GiB 49.79 GB)
Used Dev Size : 48620608 (46.37 GiB 49.79 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Thu Aug 21 19:40:54 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : e5df81f7:3aab94ea:cc328929:8db8e0da
Events : 0.26
Number Major Minor RaidDevice State
0 8 19 0 active sync /dev/sdb3
1 8 35 1 active sync /dev/sdc3
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Fwd: Bug#495949: grub-common: grub-probe segfaults]
2008-08-21 18:05 ` [Fwd: Bug#495949: grub-common: grub-probe segfaults] Felix Zielcke
@ 2008-08-24 10:05 ` Felix Zielcke
2008-08-27 9:40 ` Felix Zielcke
1 sibling, 0 replies; 3+ messages in thread
From: Felix Zielcke @ 2008-08-24 10:05 UTC (permalink / raw)
To: Jean-Luc Coulon (f5ibh); +Cc: The development of GRUB 2
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
Thanks very much for your reply
Jean-Luc please make sure you're subscribed to grub-devel and then
please reply there.
If you want you can CC bugs.debian.org but it isn't needed.
Both Robert and me are actively on grub-devel too.
We're just not alone there and I don't feel myself able to trace this
down alone.
It has probable to do with your crypted LVM, but this should never ever
cause memory corruption
-------- Weitergeleitete Nachricht --------
> Von: Jean-Luc Coulon (f5ibh) <jean-luc.coulon@wanadoo.fr>
> Antwort an: Jean-Luc Coulon (f5ibh) <jean-luc.coulon@wanadoo.fr>, 495949@bugs.debian.org
> An: 495949@bugs.debian.org
> Kopie: grub-devel@gnu.org
> Betreff: Bug#495949: grub-common: grub-probe segfaults
> Datum: Sun, 24 Aug 2008 10:40:45 +0200
>
> Hi Felix
>
> Le 21.08.2008 17:29:57, Felix Zielcke a écrit :
> >
> >>
> >> There is no disk *removed*. BUT the device name of the disks
> >allocated
> >> by the system to the disks is not consistant from one boot to the
> >> other.
> >Well I mean something like that in `mdadm -Q --detail /dev/md0'
> > output:
> >
>
> Today, the disks where affected an other way:
> - sda and sdb for the raid1 and sdc for the other disk
> This way, the latest available version of grub-common (20080724) works.
>
> Attached the output of mdadm -Q -D for each of the arrays.
>
> Regards
>
> Jean-Luc
> _______________________________________________
> Pkg-grub-devel mailing list
> Pkg-grub-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
[-- Attachment #2: md0 --]
[-- Type: text/plain, Size: 703 bytes --]
/dev/md0:
Version : 00.90
Creation Time : Sun Feb 17 17:50:51 2008
Raid Level : raid1
Array Size : 232832 (227.41 MiB 238.42 MB)
Used Dev Size : 232832 (227.41 MiB 238.42 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Aug 24 10:22:47 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 19628d78:d50fb284:cc328929:8db8e0da
Events : 0.199
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
[-- Attachment #3: md1 --]
[-- Type: text/plain, Size: 703 bytes --]
/dev/md0:
Version : 00.90
Creation Time : Sun Feb 17 17:50:51 2008
Raid Level : raid1
Array Size : 232832 (227.41 MiB 238.42 MB)
Used Dev Size : 232832 (227.41 MiB 238.42 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Aug 24 10:22:53 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 19628d78:d50fb284:cc328929:8db8e0da
Events : 0.198
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
[-- Attachment #4: md2 --]
[-- Type: text/plain, Size: 703 bytes --]
/dev/md0:
Version : 00.90
Creation Time : Sun Feb 17 17:50:51 2008
Raid Level : raid1
Array Size : 232832 (227.41 MiB 238.42 MB)
Used Dev Size : 232832 (227.41 MiB 238.42 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Aug 24 10:22:54 2008
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 19628d78:d50fb284:cc328929:8db8e0da
Events : 0.198
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Fwd: Bug#495949: grub-common: grub-probe segfaults]
2008-08-21 18:05 ` [Fwd: Bug#495949: grub-common: grub-probe segfaults] Felix Zielcke
2008-08-24 10:05 ` Felix Zielcke
@ 2008-08-27 9:40 ` Felix Zielcke
1 sibling, 0 replies; 3+ messages in thread
From: Felix Zielcke @ 2008-08-27 9:40 UTC (permalink / raw)
To: The development of GRUB 2
Am Donnerstag, den 21.08.2008, 20:05 +0200 schrieb Felix Zielcke:
> The report is on http://bugs.debian.org/495949
>
Anyone on this list has an idea about this?
I'm not a guy who sees a mistake by just looking at the sourcecode.
Just having a LUKS crypto device and a logical volume on there doestn't
cause it.
grub-probe just says unknown mapping for vg-lvol0
So probable I need to reassemble the setup from Jean-Luc
Jean-Luc when and now did you create your whole LVM/CRYPT/RAID thing?
The output of cryptsetup status could be helpful too.
I only played now a bit with `mdadm' and LVM for grub but never with
`cryptsetup'
By the way I noticed that on LUKS there's a /dev/dm-0 as you have it
used for the LVM but there's a /dev/mapper/name too though that
shouldn't make a difference.
I used the dm-0 one.
--
Felix Zielcke
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-08-27 9:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1219336815.5591.0@tangerine>
[not found] ` <1219338223.4090.50.camel@fz.local>
[not found] ` <1219338766.5591.1@tangerine>
[not found] ` <1219339864.4090.58.camel@fz.local>
2008-08-21 18:05 ` [Fwd: Bug#495949: grub-common: grub-probe segfaults] Felix Zielcke
2008-08-24 10:05 ` Felix Zielcke
2008-08-27 9:40 ` Felix Zielcke
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.