Date: Sat, 11 Jul 2015 20:24:53 -0700 From: Don whY <Don.whY@gmx.com> To: Wojciech Puchar <wojtek@puchar.net> Cc: FreeBSD-Hackers Mailing List <freebsd-hackers@freebsd.org> Subject: Re: format/newfs larger external consumer drives Message-ID: <55A1DE05.4010304@gmx.com> In-Reply-To: <alpine.BSF.2.20.1507102219190.749@laptop.wojtek.intra> References: <559EDAB8.9080804@gmx.com> <alpine.BSF.2.20.1507101858480.2085@laptop.wojtek.intra> <55A00743.4080609@gmx.com> <alpine.BSF.2.20.1507102219190.749@laptop.wojtek.intra>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/10/2015 1:20 PM, Wojciech Puchar wrote: >>> >>> i would assume you will most likely store large files. >> >> For the demo application I'm writing up (to illustrate the issues >> that appliance developers might face), I would be storing large files >> (e.g., ISO's). But, some other developer/application might choose >> to use the medium for smaller files -- or even smaller media capacity. >> > so right options. > > for smaller files > > newfs -m 0 -i <put what you need here> -b 32768 -f 4096 -U > > this will mean longer fsck > > you may add -j if you like - soft updates journalling. > >> means little "mismatches" in configuration can have noticeable >> impact on the end user (e.g., he opts for finer-grained management >> and pays the price when a volume isn't properly dismounted, power >> fail, etc.) > > depends on I/O style. On random I/O it will not have big impact. I meant he pays the price when something goes *wrong*. With an appliance, you're not typically dealing with console access. Rather, expecting the device to just "Do The Right Thing". >>> newfs -m 0 -i 262144 -b 65536 -f 8192 -U /dev/yourdisk >>> >>> and it will be fast to fsck.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A1DE05.4010304>