Date: Fri, 18 Jan 2013 00:04:11 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-hackers@freebsd.org Subject: Re: stupid UFS behaviour on random writes Message-ID: <alpine.BSF.2.00.1301180002080.6205@wojtek.tensor.gdynia.pl> In-Reply-To: <103826787.2103620.1358463687244.JavaMail.root@erie.cs.uoguelph.ca> References: <103826787.2103620.1358463687244.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'd argue that using an I/O size smaller than the file system block size is > simply sub-optimal and that most apps. don't do random I/O of blocks. > OR > If you had an app. that does random I/O of 4K blocks (at 4K byte offsets), > then using a 4K/1K file system would be better. i can just use raw partition but it isn't about the question. For me it is just clearly suboptimal behavior, but if it "cannot be fixed" then fine. The case is when you store VM images on filesystem and virtual machine issues writes. Quite common case.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1301180002080.6205>