On Thu, Apr 20, 2006 at 05:10:44PM -0400, Eddie Williams wrote: > On Thu, 2006-04-20 at 16:44 -0400, Steve Feehan wrote: > > On Thu, Apr 20, 2006 at 10:07:50PM +0200, Christophe Varoqui wrote: > > > And that makes the errors go away for the LVM case. But I still > > get the kernel errors during bootup. > > > > Did you rebuild your RAM disk? If not it will scan LVM using the conf > file from the last build. No, I hadn't considered that. But looking at the content of the initramfs there is not a copy of lvm.conf in there. But I have since rebuilt the initramfs and it did not make a difference. I have not customized the default Ubuntu initramfs (other than building it for the patched kernel that I needed to build to get the dm-hp-sw module). Should I be doing anything special in the initramfs? Note that I'm not trying to put the / file system on a multipath device... I'm not nearly that ambitious. :) Also, I noticed this when the device-mapper modules are loaded from the initramfs: Begin: Loading e[42949384.440000] SCSI subsystem initialized ssential drivers[42949384.500000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@xxxxxxxxxx ... ... [42949384.620000] device-mapper: dm-multipath version 1.0.4 loaded [42949384.710000] dm_hp_sw: Unknown parameter `dm-hp-sw.c' Done. But looking at the boot text, there was something wrong with the loading of dm-hp-sw from the initramfs. It appears that the dm-hp-sw module was not successfully loaded until much later in the boot sequence. I tracked this down and fixed the problem. But still, even with dm-hp-sw loading before the SCSI devices are probed, I get a ton of SCSI errors trying to access the "ghost" devices. -- Steve Feehan -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
