Date: Mon, 26 Aug 1996 14:05:12 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: Joe Greco <jgreco@brasil.moneng.mei.com> Cc: nate@mt.sri.com (Nate Williams), michaelv@mindbender.serv.net, freebsd-isp@freebsd.org Subject: Re: Anyone using ccd (FreeBSD disk striper) for news Message-ID: <199608262005.OAA20286@rocky.mt.sri.com> In-Reply-To: <199608262002.PAA01517@brasil.moneng.mei.com> References: <199608261910.NAA19448@rocky.mt.sri.com> <199608262002.PAA01517@brasil.moneng.mei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > What I want is a solution which postpones the writes until hell freezes > > > over. Or, better yet, doesn't do them at all. > > > > Use MFS for your news spool partition. :) > > > > You *have* to write them down sometime unless you have gigabytes of > > battery backed memory. > > Why? > > Of what practical value or use is writing back data which will never be > looked at? Maybe I'm confused, but I see the discussion talking about ATIME writes, and normal writes, and there being no distinction made between when you are talking about one or the other. > Think about it: if you were to unmount your news spool and remount it -ro, > nnrpd would continue to work just fine because NOTHING ever looks at the > file atime value (which FFS can't/won't modify if you mount -ro)... and if > the only reason you are doing an update is to write back the modified atime, > what the hell is the value of doing the write? POSIX compliancy. :) I was under the impression that you didn't even want to write out the actual data itself. :) Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608262005.OAA20286>