> But that can't work. corosync (when using cman) needs cluster.conf to > start up. So if the filesystem depends on corosync you have a catch-22 > situation: the filesystem can't be mounted because corosync isn't > running
That is no problem. You can mount the filesystem, but it is read-only as long as the node does not have quorum. > and corosync can't start because the filesystem holding its > configuration isn't mounted. > > This is why cluster.conf is always read from the local disk. It's the > only thing guaranteed to be there at the time. There are ways of > holding configuration in LDAP but they are not very mature at the moment. > > A simple distributed filesystem sounds interesting though. Is it > generally available ? I can post the code if you want (it is GPL)? But do not expect too much, it is just a prototype I use too learn how corosync works. - Dietmar _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
