From owner-freebsd-hackers@freebsd.org Sun Jul 12 03:25:19 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83F81975D for ; Sun, 12 Jul 2015 03:25:19 +0000 (UTC) (envelope-from Don.whY@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 15A10AF5 for ; Sun, 12 Jul 2015 03:25:19 +0000 (UTC) (envelope-from Don.whY@gmx.com) Received: from [192.168.1.115] ([67.212.197.98]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MdKgV-1ZVvkq0ICJ-00IUuN; Sun, 12 Jul 2015 05:25:11 +0200 Message-ID: <55A1DE05.4010304@gmx.com> Date: Sat, 11 Jul 2015 20:24:53 -0700 From: Don whY User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Wojciech Puchar CC: FreeBSD-Hackers Mailing List Subject: Re: format/newfs larger external consumer drives References: <559EDAB8.9080804@gmx.com> <55A00743.4080609@gmx.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:tir9jWC8NMOusT1exvLcvFn7L6l/niVIMHZZ4hByR0+GjYlC/dR 9yfHtRpmannVTbdDxU7v5kCaajoXbrPqqoIg11bJr3gm2lVytcrq15mfqANQQ5oA+SPTP3z Pvx+2EdU4uxu4Ja1nll12nK63PDvC72nbFDOwp71dwvcebNj9zMNcBTkmw/03VgdNQnq71W TSf8+UvSypNWeFwMFUN1A== X-UI-Out-Filterresults: notjunk:1;V01:K0:9pOuhxTPXyQ=:34gisSu4Ps45Xy1aLaLqqg Ijx1hPEN8jpNNoN8VI7Q/NH+vypUH8F9uMC9gEtvogmpYh06ODXh5MaiyVqJWaZ76famdTqVm 8uRo/pUPKxMWJj0Xym+yS/KkR9cuxeEaDFgPAAQU6XQPDZLNTctC4yk00fWTkV3/P9/zjb91A ttdRT6hHPGaRTYQk/1KbIsTWy0csulaDQQnlZdXXH/Zirgr55VE2/1N3+vW4QPq6o3a2xExzf YT0VsPpIAMtAnHbhfveu5v39rnjrSYUPTXgOGDGpaHuRcVdRTqjBCDAOQmiHZKFqdX6vdod7y DyFVGGwmw9QdQhn+/Cv0xXt/4eteXfKm9j/YOiqfkrEDzkzdcxX9fV5z8QsGw90jFGbbWV9V5 xVTWxNoqWns9M6H+kvcJR9rWdzmxaOJ8EgbnZmWeMjNDwGYjSNGjGd6ZFJjAGlZHJj9XZgnH/ piqxf1DARA8H/NBBpGQP7GsyGlSSfuLJywCtTMtTZDgUwM4QDU5YvGFzJibv3yK9WLz/xHTEh VIo7x0rDo2agQcagI1cRwIQ4G4nOrz4po8r5JZHffJ+xs8CYU2zue5X1KAQyudC69qhG4KI8f BQr3+w7i+LFw4K426XOTr7a9G8hcXnAWJp71xp+zvSBklQnAlsvhqvJ0wn3ROGm3bmaqHKPlX 7F0zOK8vGPVKbSduSygwhhy+2OCKhAZXBeO++CDyubxGmf88oLNwK1pqrqnOtOOWYHkQ= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2015 03:25:19 -0000 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 -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.