From owner-freebsd-hackers@freebsd.org Fri Jul 10 17:56:42 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 663173A12 for ; Fri, 10 Jul 2015 17:56:42 +0000 (UTC) (envelope-from Don.whY@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 CA2E672 for ; Fri, 10 Jul 2015 17:56:41 +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 0MZTbR-1ZYrka2IXN-00LFfX; Fri, 10 Jul 2015 19:56:33 +0200 Message-ID: <55A00743.4080609@gmx.com> Date: Fri, 10 Jul 2015 10:56:19 -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> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:hxasPBNYjO+6fzYpO80ADn5jaeD2aBSVL9f2+i7z3TyiqTSj77U db5hh+baYN98uFyawUaP/DABT7FYc5N+NDSkXWk0CsDodF+48hP3TVP17V3HaeY2Qb+maQM aeFzu5pXLpngMwPjRQVfWSYk+c6WoOOg9SafWT3aLNtoTj2u9963dq8FjJxl9PIG34tD6u2 OFBLW+xyJkSEX++hV16xw== X-UI-Out-Filterresults: notjunk:1;V01:K0:/BDWfIkcp2g=:dyfuwNqoVgKI1nuWbkSMDM 6c+4SQmENzMW5HqvYrLflv5LTX6688JqszwGeIhMfMHXChejKp9BsAU5in2KzuBxJh4A7mCad WPJLgDl4RFePWlsHdOygzRAY0Lc9GyRR55F0JajzcO9z5ZeUGGkLwHdtEYmmRQPEwgn9x4wBK Xk5QmvT8HTeT8j8lGU+5p4MP+XVJ7BYWYxAv+JCVmo8XNUO8aBm/YLRMbJi+GYJT1WzoQPNMC uso+XuxeiRel6wgXqC1U6uYl6klIFznynEg3Res8Zeg83Ztd+PQkX+px3Vlpfle+siJ6hyWC3 MkOaCqucxFQlLbsDxIsNjeDzeCPiKFfaeH0aLLlzCRDog2jZleSFU/TbLHqsPyG/OCc/UgjBT OdT45PONDztO2dCOwyqBgch9SAAk+sluNPBgjUuBw7q5M8IcN4oAY19syI6EyAm8k26NN+3RG QfpemVo7ucILhLOEUz1q+VY9pfzLyYpYIUoN9jLAP+hgf7PunhtGYjZr0daikKJK+7EKKda6x DeKvluZROlH6+ANO9XcV6L6wZxGufAl4BMXofRSh/0QxIZV2/N9AatMDoN/mdea0K6VpLpIMX +nao1hOjEcczl4jU+KcG3sxwvcFXs6vesY/w5oip/k6T9+k/JP90FqDdzXdS8U7R31w07blOE +k6uzE618bP9t/SOfYVhNAYd0YeZaXqu0ROCBiwNzwPl4K2J4RZcNfF25wRWN8p929Ys= 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: Fri, 10 Jul 2015 17:56:42 -0000 On 7/10/2015 9:59 AM, Wojciech Puchar wrote: >> When building a filesystem (FFS) on these 1/2/3/4TB external USB >> drives, any suggestions? E.g., changing block sizes? Cut into >> multiple slices to make fsck's job easier (as well as *recovery*)? > > 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, I'm trying to prepare a list of criteria to guide them in configuring the medium as well as their expectations from it. E.g., the "big" drives I mentioned tend to use 4K "sectors" while smaller/legacy drives are 512. I don't know if this can all be transparent to the user or if the developer needs to take special steps based on the actual medium being supported. The limited bandwidth of the comm channel to the (external) drive 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.) > newfs -m 0 -i 262144 -b 65536 -f 8192 -U /dev/yourdisk > > and it will be fast to fsck. >