Bug#401393: [Fwd: Bug#401393: Please test the attached patch for against lilo 22.7.3-1.3]

Hi John, please consider to merge this patch to LILO source. It has been sent for a Debian user. For more details about this problem, please refer to http://bugs.debian.org/401393 Thanks in advance, Sincerely, Andrés Roldán Debian Developer Key-ID: 0xb29396eb --- Begin Message --- tags 401393

Bug#401393: Please test the attached patch for against lilo 22.7.3-1.3

Il Wed, Jan 31, 2007 at 03:22:13PM +0100, Loïc Minier ha scritto: > tags 401393 + patch > stop > > Hi, > > This is a followup for Debian bug . > > Could people experiencing this bug please test the attached > lilo_22.7.3-1.4.diff against lilo 22.7.3-1.3

Bug#401393: Please test the attached patch for against lilo 22.7.3-1.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Loïc Minier wrote: Could people experiencing this bug please test the attached lilo_22.7.3-1.4.diff against lilo 22.7.3-1.3? Seems to be working on my box. At least I didn't get any error messages when running lilo, and it rebooted properly. (Tha

Bug#401393: Please test the attached patch for against lilo 22.7.3-1.3

> This is a followup for Debian bug . > > Could people experiencing this bug please test the attached > lilo_22.7.3-1.4.diff against lilo 22.7.3-1.3? > > I don't run lilo nor RAID 1, but I could verify that dmsetup() calls on > major/minor work on my devices an

Bug#401393: Bug#402511: Device nodes are not removed when devices are brought down

Hi, I see you commented in #401393 linking to #402511. On Thu, Jan 18, 2007, Frans Pop wrote: > Further analysis in http://bugs.debian.org/406697 has shown that the > reason the /dev/dm-* devices are not removed, is the fact that udevd has > already been killed by the time the crypto a

Bug#401393: Please test the attached patch for against lilo 22.7.3-1.3

tags 401393 + patch stop Hi, This is a followup for Debian bug . Could people experiencing this bug please test the attached lilo_22.7.3-1.4.diff against lilo 22.7.3-1.3? I don't run lilo nor RAID 1, but I could verify that dmsetup() calls on major/mi

Bug#401393:

aargh, I confused /dev/dm-* en /dev/md-* sorry again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#401393: rm /dev/md-* doesn't work after reboot

I'm getting confused now. lilo didn't work, I removed /dev/md-* and it did work. After a reboot lilo didn't work anymore... This is tested on two machines, lilo 22.7.3 and 22.6.1. both machines: 2.6.18-3-686 #1 SMP, udev 0.103-1 lilo -t -v -v LILO version 22.7.3 (test mode), Copyright (C) 1992-

Bug#401393: lilo should ignore /dev/dm-*?

Quoting Andreas Barth <[EMAIL PROTECTED]>: Summary is that it's probably easiest if lilo would just ignore /dev/dm-* - is that ok from "it does not have other side-effects" as well? I'll check that but I think that's not a problem. If you are right, it will be implemented. Thanks for the he

Bug#401393:

Sorry for bothering. rm /dev/md-* Worked out for me. (big relieve)

Bug#401393:

Same problem here with Lilo 22.6.1 and 22.7.3 The problems first appeared after upgrading to the newest initramfs-tools. The upgrade didn't work I had to uninstall all old kernel images and reinstall the running kernel image. The problem was probably caused earlier but I didn't use Lilo until the

Bug#401393: lilo is confused by /dev/dm-*

Package: lilo Version: 1:22.7.3-1 Followup-For: Bug #401393 lilo is definetely confused by /dev/dm-* devices. If I remove /dev/dm-0 (my root LV) lilo correcly opens /dev/mapper/control and issues DM_TABLE_STATUS: 8870 open("/dev/mapper/control", O_RDWR|O_LARGEFILE) = 4 [...] 887

Bug#401393: Acknowledgement (Previously working LVM setup mysteriously broken.)

I noticed the NEWS.Debian item about RAID problems. My problem is not fixed with this version -- I have to remove /dev/dm-* to get lilo to work. Daniel signature.asc Description: Digital signature

Bug#401393: Previously working LVM setup mysteriously broken.

Hi! I have also just experiened this: device-mapper: table ioctl failed: No such device or address Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed What I did: install etch with root-on-lvm from the rc1 installer. Boot up. dist-upgrade to newest etch (udev 103, kernel 2.6.18-something...

Bug#401393: Previously working LVM setup mysteriously broken

Looks like my BR http://bugs.debian.org/402511 against lvm-common is related to this issue. The issue itself seems to be based in lvm2 and udev. David Härdeman pointed me to https://bugzilla.novell.com/show_bug.cgi?id=178321 which may have a (partial) fix for this issue in https://bugzilla.novel

Bug#401393: info for those of us in the dark

Could you please let us know an approximate ETA for getting 22.7.3 into the archive? I also want to make a request to get it into Etch. I am running some machines that I wanted to settle onto Etch upon the release that need the update for this dev mapper problem. wt -- Warren Turkal (w00t)

Bug#401393: Got the same issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just adding myself here to receive bug notifications (hope that actually works by adding a notice), I have the same issue than the first submitter, LVM on RAID1 and lilo fails with: device-mapper: table ioctl failed: No such device or address Fatal:

Bug#401393: normal severity?

I'm preparing an upload with the latest LILO upstream version. It has some changes related to RAID1 problems. I can bring you the preliminar packages if you wish though. This message was sent using IMP, the Internet Messaging Pro

Bug#401393: plans

Are there any plans for fixing this? Is a fix in progress? I have several machines using lvm root, and I am willing to help in any way to get a fix developed and distributed. Please let me know what I can do to help. Thanks, wt -- Warren Turkal (w00t) -- To UNSUBSCRIBE, email to [EMAIL PROT

Bug#401393: normal severity?

I was wondering why this bug is normal serverity when it causes previously working systems to fail to boot. Is there any workaround for this bug with root on LVM? Thanks, wt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#401393: Previously working LVM setup mysteriously broken.

On Fri, December 8, 2006 10:31, Loïc Minier said: > On Fri, Dec 08, 2006, David Härdeman wrote: >> Don't mix up boot-on-raid and boot-on-device-mapper, they are two >> different things using different kernel subsystems (md and dm). > > Err, md is dm based, right? Nope, see http://lwn.net/Articles

Bug#401393: Previously working LVM setup mysteriously broken.

On Fri, December 8, 2006 4:12, Daniel Burrows said: > On Thu, Dec 07, 2006 at 09:33:33AM +0100, Loïc Minier <[EMAIL PROTECTED]> was > heard to say: >> some trivia first: >> - Debian's lilo is patched with an unofficial patch for device-mapper >>support which was not updated since mid 2005 >>

Bug#401393: [EMAIL PROTECTED]: Bug#392623: Previously working LVM setup mysteriously broken.]

Loïc Minier wrote: > On Thu, Dec 07, 2006, Sjoerd Simons wrote: >> In this case i'd say it's something lilo should work around by preferring >> /dev/mapper/* devices. > > That's the workaround I proposed as well, but I'm not using lilo > anywhere and don't feel like I'm empowered to do some lilo

Bug#401393: Previously working LVM setup mysteriously broken.

Hi, some trivia first: - Debian's lilo is patched with an unofficial patch for device-mapper support which was not updated since mid 2005 - Debian just hits the problem, but it seems to be a common problem if I look at google queries; see also: https://launchpad.net/distros/ub

Bug#401393: Previously working LVM setup mysteriously broken.

Loïc Minier wrote: [...] > Could you send a lilo run in verbose mode and your lilo.conf to the > bug? A "dmsetup ls" would be nice as well. Ok, so here are lilo.conf, dmsetup ls, and some lilo output: - lilo-t-v.bad - lilo-t-v5.bad - lilo-t-v.ok Cheers Harry boot=/dev/sda3 root=/dev/mapper/vg

Bug#401393: Previously working LVM setup mysteriously broken.

Package: lilo Version: 1:22.6.1-9 Severity: grave My system has a somewhat unusual setup: I'm using lvm on RAID1. Sometime recently, lilo just quit working: [EMAIL PROTECTED]:~$ sudo lilo Warning: COMPACT may conflict with LBA32 on some systems device-mapper: table ioctl failed: No such device