All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: "Jean-Luc Coulon (f5ibh)" <jean-luc.coulon@wanadoo.fr>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Fwd: Bug#495949: grub-common: grub-probe segfaults]
Date: Sun, 24 Aug 2008 12:05:28 +0200	[thread overview]
Message-ID: <1219572328.4133.14.camel@fz.local> (raw)
In-Reply-To: <1219341901.4090.69.camel@fz.local>

[-- 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


  reply	other threads:[~2008-08-24 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2008-08-27  9:40         ` Felix Zielcke

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=1219572328.4133.14.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.org \
    --cc=jean-luc.coulon@wanadoo.fr \
    /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.