Re: [9fans] Fossil robustness

2010-04-20 Thread Anthony Sorace
Both fossil and kfs seem like the wrong tool for your job. In addition to the robustness questions, they (especially fossil) include features you're not going to get anything out of in your environment. If you use something like paqfs(4) or sacfs(4) (not sure which is more appropriate) you'll get

Re: [9fans] Fossil robustness

2010-04-20 Thread Adriano Verardo
erik quanstrom wrote: I've made a customized install procedure copying from the standard one. Where can i find a procedure for kfs to copy from? Can kfs be configured to be absolutely insentive to hard power down ? "absolutely" is too strong. if one turns off atime with kfscmd/atime, it

Re: [9fans] Fossil robustness

2010-04-20 Thread erik quanstrom
On Tue Apr 20 06:46:54 EDT 2010, a.vera...@tecmav.com wrote: > Hi all. > > I'm building an industrial application hosted by several independent > cpu server, each of them booted from a CFlash on sdD0. > > The application doesn't write on sdD0 and there are no redirection on > local files in t

Re: [9fans] Fossil robustness

2010-04-20 Thread erik quanstrom
> I've made a customized install procedure copying from the standard one. > Where can i find > a procedure for kfs to copy from? Can kfs be configured to be > absolutely insentive to hard power down ? "absolutely" is too strong. if one turns off atime with kfscmd/atime, it is pretty robust. s

Re: [9fans] Fossil robustness

2010-04-20 Thread John Soros
Yes, i've had a lot of problems with fossil when it gets killed. My issue was with wikifs that had some sort of memory leak i suspect, it would fill up the memory, and then fossil would crash and/or get corrupted. I had an idea for a project to use mycroftiv's rootless kernel images and have a s

Re: [9fans] Fossil robustness

2010-04-20 Thread Adriano Verardo
John Soros wrote: Hello Adriano, Have you disabled all snapshotting features? Usiong open -r? How are you starting fossil, what's your configuration? Hi, John fsys main open -AWVP -c 3000 srv fossil srv -p fscons on /dev/sdD0/fossil open -r guarantees that fossil doesn't do physycal writ

Re: [9fans] Fossil robustness

2010-04-20 Thread Adriano Verardo
maht wrote: On 20/04/2010 11:45, Adriano Verardo wrote: Hi all. I'm building an industrial application hosted by several independent cpu server, each of them booted from a CFlash on sdD0. The application doesn't write on sdD0 and there are no redirection on local files in the cpurc scrip

Re: [9fans] Fossil robustness

2010-04-20 Thread John Soros
Hello Adriano, Have you disabled all snapshotting features? Usiong open -r? How are you starting fossil, what's your configuration? -- John Soros On Tuesday 20 April 2010 12:45:09 Adriano Verardo wrote: > Hi all. > > I'm building an industrial application hosted by several independent > cpu

Re: [9fans] Fossil robustness

2010-04-20 Thread maht
On 20/04/2010 11:45, Adriano Verardo wrote: Hi all. I'm building an industrial application hosted by several independent cpu server, each of them booted from a CFlash on sdD0. The application doesn't write on sdD0 and there are no redirection on local files in the cpurc scripts. In this

[9fans] Fossil robustness

2010-04-20 Thread Adriano Verardo
Hi all. I'm building an industrial application hosted by several independent cpu server, each of them booted from a CFlash on sdD0. The application doesn't write on sdD0 and there are no redirection on local files in the cpurc scripts. In this particular situation fossil should be actuall