On Wed, 21 Mar 2007 10:46:30 -0700 Adam Megacz <[EMAIL PROTECTED]> wrote:
> > Davor Ocelic <[EMAIL PROTECTED]> writes: > > more concerned about the fact that AFS doesn't write files > > until you close() them. > > ... or fsync() them, which databases do at the points where they need > to assume data has been written to the disk. But still... > > > In any case, we'd be introducing a huge uncertainity into an area > > that people struggled to make flawless and reliable. > > Yes, absolutely... mysql/postgres are reallycomplex, and AFS is > reallycomplex, and almost nobody else out there is using them > together. It wouldn't be wise to be a "canary in the coal mine" on > this one. Since there's been not too much input on this one, I suppose the users don't have much objection to databases in AFS as long as they work. Furthermore, since we've spent a greal deal of time to make it work that way, and since our databases are 500 MB in total, we are going tol go that way and test-drive the whole idea. We will fsync or re-start mysql/postgres every day to trigger data write to disks, and save database dumps to respective users' AFS volumes, in case of any problems.. -doc _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
