From owner-freebsd-stable@freebsd.org  Wed Dec 14 21:59:20 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 5016DC8019C
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 14 Dec 2016 21:59:20 +0000 (UTC)
 (envelope-from jakub_lach@mailplus.pl)
Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15])
 by mx1.freebsd.org (Postfix) with ESMTP id 41C11867
 for <freebsd-stable@freebsd.org>; Wed, 14 Dec 2016 21:59:19 +0000 (UTC)
 (envelope-from jakub_lach@mailplus.pl)
Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37])
 by mbob.nabble.com (Postfix) with ESMTP id BB829380F243
 for <freebsd-stable@freebsd.org>; Wed, 14 Dec 2016 13:45:59 -0800 (PST)
Date: Wed, 14 Dec 2016 14:59:19 -0700 (MST)
From: Jakub Lach <jakub_lach@mailplus.pl>
To: freebsd-stable@freebsd.org
Message-ID: <1481752759263-6152018.post@n6.nabble.com>
Subject: Should 4K AF disk with FAT32 (newfs_msdos -F32 -S 4096) be
 unmountable?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2016 21:59:20 -0000

Hello, 

FreeBSD 11.0-STABLE #0 r309991 here, if I use -S 4096 the mount_msdosfs
complains about "mount_msdosfs: /dev/ada1s1: Invalid argument".

Is this expected?

See example:

$ sudo newfs_msdos -F32 -S 4096 /dev/ada1s1                         
Password:
newfs_msdos: trim 3 sectors to adjust to a multiple of 63
/dev/ada1s1: 244182720 sectors in 3815355 FAT32 clusters (262144
bytes/cluster)
BytesPerSec=4096 SecPerClust=64 ResSectors=4 FATs=2 Media=0xf0
SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=244190205 FATsecs=3726
RootCluster=2 FSInfo=1 Backup=2
$ sudo mount_msdosfs -o large /dev/ada1s1 /mnt/                                                    
Password:
$ sudo mount_msdosfs: /dev/ada1s1: Invalid argument
$ sudo newfs_msdos -F32 /dev/ada1s1  
Password:
newfs_msdos: trim 24 sectors to adjust to a multiple of 63
/dev/ada1s1: 1953044736 sectors in 30516324 FAT32 clusters (32768
bytes/cluster)
BytesPerSec=512 SecPerClust=64 ResSectors=32 FATs=2 Media=0xf0
SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=1953521640 FATsecs=238409
RootCluster=2 FSInfo=1 Backup=2
$ sudo mount_msdosfs -o large /dev/ada1s1 /mnt/                     
Password:
$

etc...



--
View this message in context: http://freebsd.1045724.x6.nabble.com/Should-4K-AF-disk-with-FAT32-newfs-msdos-F32-S-4096-be-unmountable-tp6152018.html
Sent from the freebsd-stable mailing list archive at Nabble.com.