From: Gordan B. <go...@bo...> - 2007-10-11 16:50:20
|
On Thu, 11 Oct 2007, Marc Grimme wrote: >> It throws up a worrying error when it boots: >> GFS: fsid=cluster:root.0: warning: assertion >> "gfs_glock_is_locked_by_me(ip->i_gl)" failed >> GFS: fsid=cluster:root.0 function = gfs_readpage >> GFS: fsid=cluster:root.0 file = >> /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/ops_address.c, >> line 279 >> GFS: fsid=cluster:root.0: time = 1192119131 >> >> I wonder if this may be caused by a file system perhaps not having been >> cleanly unmounted on a previous try while I was building it... > > Perhaps just fschk it when you're in the initrd. Yup, just did. Some minor things were broken with the fs metadata. But when I reboot, I still get a similar message when HALd loads. I wonder if I can safely switch that off - assuming that's causing it... Now, in theory, I should be able to bring up another node on the same file system. All I would need to do is clone the /boot partition to the other box, and it should just come up. What do I need to do to achieve this, and can it all be done with the one node that is already running? I'm assuming that I'll have to do something like: mount --bind /cluster/cdsl/4/ /cdsl.local/ As far as unsharing things under /var, I _think_ only /var/lock actually needs to be unshared. Can I do this with the running image with: com-mkcdsl -r / -a /var/lock ? Thanks. Gordan |