Hi,
Michael Loftis wrote:
The theory only translates if you're using a JOURNALED file system. Linux ext3, reiserfs.... AIX JFS, Sun/others veritas are all examples of this. AFAIK FreeBSD hasn't any journalling file systems,
Hmm, some say the use of softupdates preclude a journaling filesystem (see for instance http://kerneltrap.org/node.php?id=6). It's all a bit different with FreeBSD :-)
That said, the machine shouldn't' have crashed in the first place, but you are running 5.x which is clearly labeled as *NOT* production (4.10 for that)... All of my produciton boxen are 4.x based (of the FreeBSD herd)
You are right - 5.x is not stable yet, but 5.3 is very close to it. Since 5.3 is coming we thought it would be easier to install with 5.2.1 and upgrade to 5.3 rather then use 4.10 and upgrade that... And we might indeed face a 5.2.1-bug, that's why I mentioned the "SMP", "3G" and "GEOM" things, but might as well be something else with 5.x.
Something else that was a vote for 5.x was the filesystem; 4.10 does not have UFS2.
Apart from solving the issues we have with the machine I think we'd really look at the options for having redundany in application, as sketched in the "High availability ... again" subject :-) Maybe we'd install 5.3-BETA on the platform (I'll discuss it with another FreeBSD expert here :-))
Jure PeÄ?ar wrote:
Well, I don't know if it needs to be murder or some extension in the storage or something, but that's roughly my idea indead; synchronising two (or more? that's harder maybe) servers, just like doing an imapsync or rsync, but then... well, better! :-) (And without losing states and so forth.)>The only high availability i see here is the google way. Cyrus is >offering you that with the 'murder' component.
That's not really availability, but distributed risk.
Exactly ... with murder taking care of keeping duplicated mailboxes in sync
over a pool of backend machines (as i mentioned in the other mail), this
would be perfect for all of us, i guess.
The SPOF of the SCSI controller in the RAID box I'm willing to accept, but the filesystem is a bit harder.
I'm curious what cyrus developers think of this, and I'm interested in what we can do to help.
Paul
--- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
