From owner-freebsd-questions@FreeBSD.ORG Wed Jun 25 20:48:23 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 907057F3 for ; Wed, 25 Jun 2014 20:48:23 +0000 (UTC) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 691C923E3 for ; Wed, 25 Jun 2014 20:48:23 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id g10so2117114pdj.0 for ; Wed, 25 Jun 2014 13:48:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=cLfRTEbcIzeXcUmxtA6Y8oXHuceTEFeJmq+imDJVor8=; b=J48fAspr3WgJYFXBSys81DF9tk009q1w+VF4AMFllqFMXCx9ADeN0kvs/aZpO8ydCS lspIyP1ROU4GdwcFwoJMjrlf6iW+lGcT3Hi3Vk4lSkloJ3EEmGeTf5lnRcQMQ2KYlZQS PnRehnYph4ubsZysdekcSx+MIalBc4HDj7kjd0K0SPkb79XQbrxh6aw2bmbdLZQPgrGD ureVpcodWs+hnwbsEL2mJDIhQ2sq7/4cgXAIQyJ18i/D313lI/wFC8FcuMSXlYZtQodP CUI751/+eaBWygf1Vr+4V0wYeCB8Taxb25DMCPp/JAUkCHOBIc0Atz0QlR9eDht39lzd 3raw== MIME-Version: 1.0 X-Received: by 10.68.164.100 with SMTP id yp4mr14957122pbb.136.1403729303065; Wed, 25 Jun 2014 13:48:23 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.134.4 with HTTP; Wed, 25 Jun 2014 13:48:23 -0700 (PDT) Date: Wed, 25 Jun 2014 13:48:23 -0700 X-Google-Sender-Auth: T2GrylBEXripgpM_HgKYxFRkgkc Message-ID: Subject: Re: Cannot create files on exfat card / 10-stable From: Kevin Oberman To: questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: Mathias Picker X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2014 20:48:23 -0000 > Hi all, > > I just got my first exfat formatted sdxc card. > > If I mount it with (as root) mount.exfat /dev/da2s1 /mnt I can read the > content, create *directories*, but *not files*??? > > > root@marcopolo:/mnt # touch test1 > touch: test1: Invalid argument > root@marcopolo:/mnt # mkdir test1 > root@marcopolo:/mnt # touch test1/test > touch: test1/test: Invalid argument > root@marcopolo:/mnt # ll -d test1 > drwxr-xr-x 1 root wheel 131072 16 Feb 19:46 test1/ > root@marcopolo:/mnt # ll test1 > total 0 > > > > Shouldn't this work? > > I rebuilt fusefs-lib and fusefs-exfat with gcc48, same result... > > This is on a recent stable: > marcopolo% uname -a > FreeBSD marcopolo 10.0-STABLE FreeBSD 10.0-STABLE #14 r261827: Thu Feb > 13 13:13:01 CET 2014 mathiasp@marcopolo:/usr/obj/usr/src/sys/GENERIC > amd64 > > The card is a Sandisk Extreme MicroSDXC 64Gb. Works fine in my phone. > > Any tips, hints, experiences? > > Thanks, Mathias I have no answer as I found this message in the archive while researching the root cause of the problem. Workaround: After writing to the device on FreeBSD, put the card into a Windows system. (It will also be usable to write to the device.) Open an explorer (not Internet Explorer) window Right click on the ExFAT device Select "Properties" In the Properties window, select the "Tools" tab In the tools window click "Check now" In the disk check window click start No errors should be found, but the disk will now be writable on Windows. Note that the directories you appeared to be creating on FreeBSD will be gone. Eject the media and mount it on the FreeBSD system I t will be writable until it is re-mounted. I believe the problem is that unmounting the file system fails to mark the fs as clean. You might notice that a message that the device was not cleanly dismounted is printed to the console and messages when the device is re-mounted on FreeBSD. There is no fsck for ExFAT, so I need to use Windows to do the same job. It looks like all that is needed is to clear the second bit of byte 106 of the VBR (block 0). I will try this some day when I am feeling brave. I'd love to see this fixed -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com