[Cooker] Re: Re: Re: lvm and devfs not working
On Mon, Sep 03, 2001 at 03:44:04PM +0400, Borsenkow Andrej wrote: This comes because of mknod in vgscan. Correct. From devfs point of view, both mknod and devfs_register means the same. Meaning on a system with devfs mounted, the kernel reroutes (or does similar) mknod(2) to devfs_register when it's done on the devfs filesystem? And you are not expected to use both at the same time (for the same device in any case). Well, that would make sense. Here activating VG tries to register devfs names that were already created by vgscan. Strictly speaking, it is harmless. I don't so much care about the errors as much as I care that I don't have /dev/volume group/* entries. If I had the latter, and not the former I would write it off to old lvm code and hope that it goes away when mdk updates. Yes, but still devfs exists just once. Mounting it just makes it user-visible - but as long as devfs is conpiled in kernel, *all* device operations use devfs. It does not depend on its mounted state. So remounting devfs should not (module bug) make any difference. But does any nodes created after devfs is mounted disappear when it is (unmounted and) remounted? The system boots fine onto the LVM based root filesystem. The problem is that the device nodes in /dev/VG (group, lvol1 and 1) are missing an uncreatable. To make sure - is it root device? What do you mean? What test do you want me to run. Your question might make more sense to me when I see what test you want to see the results of. Then it could explain something. Is it possible to download your installer with LVM root support? I would give it a try. Theoretically, I can package something for you. I would give you the files to replace in your cooker to do lvm-root install. It is not complete however as I am still trying to figure out the gyrations needed for the initrd. You need to replace some installer files, the lilo rpm and eventually, the mkinitrd rpm. b. -- Brian J. Murrell
RE: [Cooker] Re: Re: Re: lvm and devfs not working
Yes, but still devfs exists just once. Mounting it just makes it user-visible - but as long as devfs is conpiled in kernel, *all* device operations use devfs. It does not depend on its mounted state. So remounting devfs should not (module bug) make any difference. But does any nodes created after devfs is mounted disappear when it is (unmounted and) remounted? No. It is just like (u)mounting harddisk partition. Contents of harddisk is there is it mounted or not. Mounting it makes it accessible to you, umounting it hides it from you. Devfs is initialized on boot; if it is used (compiled in) then every driver that is devfs-aware creates entries there. These entries exist even if devfs is not mounted. Mounting it (devfs) just makes them visible to you. The system boots fine onto the LVM based root filesystem. The problem is that the device nodes in /dev/VG (group, lvol1 and 1) are missing an uncreatable. To make sure - is it root device? What do you mean? What test do you want me to run. Your question might make more sense to me when I see what test you want to see the results of. Is the group VG the group that contains root volume? I do not want you to run any tests yet because I do not know yet what exactly to test. But I can see the only possible case for this error and only if the group VG was already created before devfs was remounted. Then it could explain something. Is it possible to download your installer with LVM root support? I would give it a try. Theoretically, I can package something for you. I would give you the files to replace in your cooker to do lvm-root install. It is not complete however as I am still trying to figure out the gyrations needed for the initrd. You need to replace some installer files, the lilo rpm and eventually, the mkinitrd rpm. I probably won't find time to try it until weekend anyway. Still, if you could put it on Web somewhere with short readme how to use the stuff ... -andrej
Re: [Cooker] Re: Re: Re: lvm and devfs not working
Borsenkow Andrej wrote: But does any nodes created after devfs is mounted disappear when it is (unmounted and) remounted? No. It is just like (u)mounting harddisk partition. Contents of harddisk is there is it mounted or not. Mounting it makes it accessible to you, umounting it hides it from you. Devfs is initialized on boot; if it is used (compiled in) then every driver that is devfs-aware creates entries there. These entries exist even if devfs is not mounted. Mounting it (devfs) just makes them visible to you. Hmmm, if some files are in /mnt/cdrom, and you mount your CDROM drive, then the files are hidden by the CD files. Hence, if devfs is just like a harddisk partition, dev nodes you create by hand with mknod will be hidden as well... Are you sure that they are still visible? Grégoire
