From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 14 Aug 2009 00:14:29 -0600 From: Lyndon Nerenberg To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: <7d3530220908131823u1d5e3b9bk22632a1cce07f38b@mail.gmail.com> Message-ID: References: <14ec7b180908131755t21bab17aua928e15f751082fb@mail.gmail.com> <47a50044bb220c4db0592a2aacb694f6@quanstro.net> <7d3530220908131823u1d5e3b9bk22632a1cce07f38b@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [9fans] file server? Topicbox-Message-UUID: 49030710-ead5-11e9-9d60-3106f5b1d025 > This is what we do at Sandia. We have one machine which serves > cpu/auth/file, but the actual Venti disks are in a Coraid connected > via GigE. The fossil disk is in the server, but if it dies we can just > build a new one. Which reminds me of an often overlooked but important point: Save your fossil vac scores on another machine! Without them, your seperate venti server is JBOD :-P Well, not quite. You can eventually find the right vac score, but you have to manually mount each and every score in the venti until you find the right one. See /sys/src/cmd/venti/words/dumpvacroots. You could probably semi-automate the process by writing a script that mounted each of the scores in turn, checking the mtime of something like /sys/log/timesync in each, and sorting the vac scores accordingly. On my setup I aux/clog the fileserver console to a u9fs mounted directory on a UNIX server. You could also cobble something up that scans the fossil console for vac scores and emails them to an offsite address. --lyndon