Date: Fri, 27 May 2005 14:55:30 -0400 From: Garrett Wollman <wollman@csail.mit.edu> To: Scott Long <scottl@samsco.org> Cc: FreeBSD Current <freebsd-current@FreeBSD.ORG> Subject: Re: Disable read/write caching to disk? Message-ID: <17047.27938.106072.257899@khavrinen.csail.mit.edu> In-Reply-To: <429763B0.2060705@samsco.org> References: <4295D51F.50106@centtech.com> <429606D9.6080602@cs.tu-berlin.de> <42960ACB.7090801@cs.tu-berlin.de> <42960CFE.4060307@centtech.com> <42960F8F.2050109@samsco.org> <42961195.30608@centtech.com> <429613FB.80100@samsco.org> <42968AD4.3020603@centtech.com> <A70C5E4F-D9F9-4756-8AC2-591462E338DE@shire.net> <4296997C.9030700@samsco.org> <20050526235852.M54386@lexi.siliconlandmark.com> <42969C1B.5010301@samsco.org> <17047.25282.72131.519040@khavrinen.csail.mit.edu> <429763B0.2060705@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Fri, 27 May 2005 12:15:12 -0600, Scott Long <scottl@samsco.org> said: > Well, having a writer is pointless if the readers are stuck on a > snapshot. Depends on the sort of problem you're trying to solve. If your business process already involves a "release" mechanism, then it should integrate quite well (just need to tell the clients to mount a new snapshot). Obviously this doesn't help for something like a clustered database. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17047.27938.106072.257899>