From: Gordan B. <go...@bo...> - 2007-10-11 11:40:32
|
On Thu, 11 Oct 2007, Marc Grimme wrote: >>>> Just looking through the initrd init script - what is supposed to be in >>>> /etc/sysconfig/comoonics-chroot ? It's mentioned in the comments, but I >>>> don't see it referenced in the actualy code. >>> >>> If you have a local disk in your server you can use it to move all the >>> files on it and save some memory. >>> >>> This can either be done configured in /etc/sysconfig/comoonics-chroot >>> installed via comoonics-bootimage-compat (or something use: yum search >>> comoonics-bootimage) or with the cluster.conf section . >>> >>> <chrootenv mountpoint="/var/comoonics/chroot" fstype="ext3" >>> device="/dev/vg_local/lv_chroot" >>> chrootdir="/var/comoonics/chroot"/> >>> >>> All services needed for the cluster outside the sharedroot will be >>> running there. >> >> So, it's effectively an initrd replacement? Doesn't the initrd get >> de-allocated once the shared root is mounted? > > No completely. The initrd or better the memory disk will also be used after > the init in initrd has given over to init on sharedroot. Because fencing and > the whole cluster-com which is running in userspace cannot run on a cluster > filesystem that might get froozen when problems are at hand. So we also > introduced a way to migrate the ramdisk on localdisks. That is the chrootenv > which is only copy of the initrd where services like fenced and the like run > on. So, what does the content of the /etc/sysconfig/comoonics-chroot need to be to make use of this? What FS should this be on? Presumably every cluster node would have this on it's local disk, then. Does this need to be build with something like the initrd image? Are there any docs on this, so I can read up on it before asking too many questions? :^) Gordan |