From: Gordan B. <go...@bo...> - 2008-11-22 15:51:43
|
Marc Grimme wrote: > But why not go this way: > There is a method/function "clusterfs_services_start" which itself calls > ${clutype}_services_start which should be implemented by > etc/${rootfs}-lib.sh. Your $rootfs should be glusterfs and therefore there > should be a library glusterfs-lib.sh. The function clusterfs_services_start > should do all the preparations to mount the clusterfilesystem and could also > mount a local filesystem as a prerequisite. So I would put it there. > A rootfs can be specified as follows: > <rootvolume name="/dev/whicheverdeviceyoulike" fstype="glusterfs"/> OK, this solution wins on the grounds that remapping the chrootenv seems to confuse glusterfs. But ${clutype}_services_start is dependent on ${clutype}, which is returned from getCluType(), which always returns "gfs". Will that not break things? From what you said, if I have the following entry: <rootvolume name="/etc/glusterfs/root.vol" fstype="flusterfs"/> $rootfs come from $fstype. Is that right? Or from <rootsource name="glusterfs">? Or somewhere else entirely? Thanks. Gordan |