> >>> 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. > > > > This is possible because it is a distributed filesystem, and each > node > > has all data locally (as opposed to shared filesystems). > > > > > Nice. > > It's similar to what VMS does to read node & cluster configuration, it > mounts the filesystem readonly, gets the config, dismounts it and > continues booting. I did once suggest something like that but it wasn't > liked for some reason.
The only problem I see is that you can't modify anything when you do not have quorum. So it must be possible to overwrite setting somehow - either by specifying environment variables, or read a second config file stored locally. What other problems can arise? - Dietmar _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
