Date: Fri, 28 Mar 2008 22:03:35 +0100 From: "Ivan Voras" <ivoras@freebsd.org> To: "David Malone" <dwmalone@maths.tcd.ie> Cc: freebsd-stable@freebsd.org Subject: Re: Question about file system checks Message-ID: <9bbcef730803281403m3f5f71a8u5d29628828b5ae26@mail.gmail.com> In-Reply-To: <20080328153851.GA76472@walton.maths.tcd.ie> References: <47EBA3AB.40307@infracaninophile.co.uk> <f9ae3129fa235b31251ec97bc12c1e78@localhost> <200803280029.08136.danny@ricin.com> <fshdv1$jbt$1@ger.gmane.org> <20080328142843.GD28690@dan.emsphone.com> <fsj2mo$dgc$1@ger.gmane.org> <20080328153851.GA76472@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28/03/2008, David Malone <dwmalone@maths.tcd.ie> wrote: > On Fri, Mar 28, 2008 at 04:26:16PM +0100, Ivan Voras wrote: > > All were tested within the same time: 50 seconds. Details: the machine > > being tested was connected to a "reporter" machine via plain crossover > > cable, the reporter had a TCP server and the tested machine had a TCP > > client that run a tight loop of IO operations, single threaded, randomly > > choosing between creating files and directories, appending to them and > > changing (a random amount of data in a random position) them, then > > sending to the server a description (log) of each IO operation after it > > has been done. These were several Python scripts I wrote. > > Our of curiosity, if you call fsync on some subset of the files > after creating them, do they all the files on which fsync completed > exist after the fsck? It should be easy to check, but I don't have the hardware any more so I can't. For what it's worth, files were opened and closed for the duration of the operations. I agree that fsync-ing files should make them more persistent.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730803281403m3f5f71a8u5d29628828b5ae26>