FUSE exfat 0.9.0 OS X 10.5.8

[JHPArizona]

I have downloaded the source, compiled, and installed exFAT. I am able
to mount an external USB drive via the command line, but can not get a
directory listing. I get the following error:
jim$ ls /mnt/jim-freeagent/
ls: : Input/output error

Here is all the output from using exFAT including showing that the
drive is mounted:
Mount the drive:
jim$ sudo mount -t exfat-fuse -o allow_other /dev/disk1s1 /mnt/jim-
freeagent
FUSE exfat 0.9.0

Output of mount commannd:
jim$ mount/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local)
fdesc on /dev (fdesc, union)
map -hosts on /net (autofs, automounted)
map auto_home on /home (autofs, automounted)
/dev/disk0s3 on /Volumes/OSX_SL (hfs, local, journaled)
/dev/disk3s10 on /Volumes/JimsDrive (hfs, local, nodev, nosuid,
journaled, noowners)
vfstool@fuse0 on /private/tmp/368/C (fusefs, nodev, noexec, nosuid,
synchronous, mounted by jim)
/dev/disk2s10 on /Volumes/FannEnv_Backups (hfs, local, nodev, nosuid,
journaled, noowners)
/dev/disk1s1 on /mnt/jim-freeagent (fusefs, synchronous)

I can umount the drive and the mount command will show that it is not
mounted.
But if I can not get a directory listing off of the drive it does not
do me any good. I installed the exFAT patch on Windows XP and
formatted a 320GB drive. Windows can recognize and write to the disk
while the Mac (OS X 10.5.8) can do neither.

I was reading other postings here and the -d does not work in my
implementation (does not mount drive).

I can test anything you want me to try. My main reason for going with
exFAT was large file (>4GB).

Thanks, Jim

[Andrew Nayenko]

Mounting with the -d key will fail if you call mount instead of
mount.exfat-fuse because mount does not recognize it. Please try to
mount your volume with the following command:
$ sudo mount.exfat-fuse /dev/disk1s1 /mnt/jim-freeagent -o allow_other -d
Note that the -d key forces it not to detach from the Terminal. If
mounting succeeds start another Terminal window and do
$ ls /mnt/jim-freeagent/
to get "Input/output error". After that switch to the Terminal where
mount.exfat-fuse was started and post the whole output here.

--
Andrew Nayenko <res...@gmail.com>

[JHPArizona]

jim-prestons-macbook-pro:~ jim$ sudo mount.exfat-fuse /dev/disk4s1 /
mnt/jim-freeagent -o allow_other -d
FUSE exfat 0.9.0
unique: 0, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.8
flags=0x00000000
max_readahead=0x00100000
INIT: 7.8
flags=0x00000000
max_readahead=0x00100000
max_write=0x00400000
unique: 0, error: 0 (Unknown error: 0), outsize: 40
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 96
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 96
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 96
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 96
unique: 0, opcode: ACCESS (34), nodeid: 1, insize: 48
ACCESS / 00
unique: 0, error: -78 (Function not implemented), outsize: 16
unique: 0, opcode: GETATTR (3), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 128
unique: 0, opcode: GETATTR (3), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 128
unique: 0, opcode: OPENDIR (27), nodeid: 1, insize: 48
unique: 0, error: 0 (Unknown error: 0), outsize: 32
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 96
unique: 0, opcode: READDIR (28), nodeid: 1, insize: 64
ERROR: invalid bitmap size: 305235 (expected 305234).
ERROR: failed to open directory `/'.
unique: 0, error: -5 (Input/output error), outsize: 16
unique: 0, opcode: RELEASEDIR (29), nodeid: 1, insize: 64
unique: 0, error: 0 (Unknown error: 0), outsize: 16
unique: 0, opcode: OPENDIR (27), nodeid: 1, insize: 48
unique: 0, error: 0 (Unknown error: 0), outsize: 32
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
Bus error

[Andrew Nayenko]

> ERROR: invalid bitmap size: 305235 (expected 305234).

This bug is already fixed in svn version. Please try the recent
version from svn (instructions:
http://code.google.com/p/exfat/wiki/QuckStartGuide) and report whether
it works for you.

--
Andrew Nayenko <res...@gmail.com>

[JHPArizona]

Hi Andrew,

Thanks! I had tried the svn version before I started this thread.
However, after re-downloading, compiling, and installing the latest
version we are getting closer :^)
I can mount and get directory listings :^), but have write permission
issues :^(

jim-prestons-macbook-pro:exfat-read-only jim$ touch /mnt/jim-freeagent/
test.tst
touch: /mnt/jim-freeagent/test.tst: Permission denied

I can write as sudo:
jim-prestons-macbook-pro:exfat-read-only jim$ sudo touch /mnt/jim-
freeagent/test.tst
jim-prestons-macbook-pro:exfat-read-only jim$ ls /mnt/jim-freeagent/
ISOs
Movies
from Bert
test.tst

jim-prestons-macbook-pro:exfat-read-only jim$ sudo rm /mnt/jim-
freeagent/test.tst
jim-prestons-macbook-pro:exfat-read-only jim$ ls /mnt/jim-freeagent/
2007 Office - Home and Student X12-30107.exe
ISOs
Movies
from Bert

I can not change permissions :^(
jim-prestons-macbook-pro:exfat-read-only jim$ sudo chmod 775 /mnt/jim-
freeagentchmod: /mnt/jim-freeagent: Function not implemented
jim-prestons-macbook-pro:exfat-read-only jim$ sudo chmod 775 /mnt/jim-
freeagent/chmod: /mnt/jim-freeagent/: Function not implemented

Here are the permissions before mounting (note: lahe is an alias for
ls -lahe)
jim-prestons-macbook-pro:exfat-read-only jim$ lahe /mnt/
total 0
drwxr-xr-x 3 root admin 102B Jun 1 09:16 .
drwxrwxr-t 39 root admin 1.4K Jun 1 09:16 ..
drwxrwxrwx 2 root admin 68B Jun 1 09:16 jim-freeagent

Here are the permissions after mounting:
jim-prestons-macbook-pro:exfat-read-only jim$ lahe /mnt/
total 256
drwxr-xr-x 3 root admin 102B Jun 1 09:16 .
drwxrwxr-t 39 root admin 1.4K Jun 1 09:16 ..
drwxr-xr-x 1 root wheel 128K Dec 31 1969 jim-freeagent


Note that it seems to have an issue with reading the modified /
created date as it is listed as Dec 31 1969. I do not know if this is
an issue with the exFAT format or the exFAT-fuse
This is the command I am mounting with:
jim-prestons-macbook-pro:exfat-read-only jim$ sudo mount -t exfat-fuse
-o allow_other /dev/disk2s1 /mnt/jim-freeagent
FUSE exfat 0.9.0

The debug mount also works the same:
jim-prestons-macbook-pro:exfat-read-only jim$ sudo mount.exfat-fuse /
dev/disk2s1 /mnt/jim-freeagent -o allow_other -d
FUSE exfat 0.9.0

There is a lot of data in the terminal after mounting. I did not post
here but can if you would like to see it.
Also, if I am posting too much information, let me know and I can
scale back. I am just trying to give you everything you may need to
help get everything working.

Bottom line is I can now use the file format :^) using sudo and will
continue to use and test. Let me know if there is anything specific
you would like me to try (short of reformating, at least until I get
the files moved to another drive). I am happy to contribute testing
time to this project. I am a very, very junior programmer but do not
have near enough skill to contribute to the code.

I can (and will) test this on Linux as that is my main platform at
home vs main platform at work is OS X.

Thanks for your effort on this project, Jim

[Andrew Nayenko]

> I can mount and get directory listings :^), but have write permission
> issues

It looks like MacFUSE behaves differently from Linux FUSE. Please try
to mount with the "umask=0" option, i.e.:
$ sudo mount.exfat-fuse /dev/disk4s1 /mnt/jim-freeagent -o umask=0
This will set permissions for files and directories to 777 and you
should be able to write to the volume without sudo. (Note that
allow_other option is not required with the recent svn version
anymore.)

> I can not change permissions

That's because exFAT does not support Unix permissions.

> Note that it seems to have an issue with reading the modified /
> created date as it is listed as Dec 31 1969.

ctime is not supported by exFAT, so it's just reported as 0. What you
see is Unix epoch + your time zone offset.

> The debug mount also works the same

Debug option just enables additional logging, don't expect any wonders
from it. :)

> Also, if I am posting too much information, let me know and I can
> scale back. I am just trying to give you everything you may need to
> help get everything working.

That's OK, detailed reports are always better.

> Let me know if there is anything specific
> you would like me to try

Just use the driver as you would do with any other FS. I have some
synthetic tests, but nothing can replace real-life testing.

> I can (and will) test this on Linux as that is my main platform at
> home vs main platform at work is OS X.

Thanks!

--
Andrew Nayenko <res...@gmail.com>

[JHPArizona]

Hi Andrew,

Thanks! I have not been back to my work office to test the new umask
setting.

I did want to update you that I have tested the drive on Linux (FC 7,
yes it is verrry old but I did upgrade from FC6 recently :^)

Seems to work great on Linux, I have had no problems. This is what I
am looking to use the drive for, transporting data from my office to
home. I am able to write to the drive in Linux. I will continue to use
it and let you know know if I run into any problems.

I will retry the drive at work on Monday and let you know what I find.

Thanks, Jim

[JHPArizona]

Hi Andrew,

Thanks so much for your help on using exFAT!

Using the -o umask=0 option works great! I will continue to use the
drive to transfer files between OS X, Linux, and Windows and let you

know if I run into any problems.

Thanks, Jim

On 6 июн, 18:37, JHPArizona <jhpariz...@gmail.com> wrote:
> Hi Andrew,
>
> Thanks! I have not been back to my work office to test the new umask
> setting.
>
> I did want to update you that I have tested the drive on Linux (FC 7,
> yes it is verrry old but I did upgrade from FC6 recently :^)
>
> Seems to work great on Linux, I have had no problems. This is what I
> am looking to use the drive for, transporting data from my office to
> home. I am able to write to the drive in Linux. I will continue to use
> it and let you know know if I run into any problems.
>
> I will retry the drive at work on Monday and let you know what I find.
>
> Thanks, Jim
>

> > šAndrew Nayenko <res...@gmail.com>

[Andrew Nayenko]

Hi Jim,

Thank you for your report. I'll make umask=0 the default.

--
Andrew Nayenko <res...@gmail.com>

[JHPArizona]

Hi Andrew,

Just wanted to drop you a note that all is going very well with using
exfat on all three operating systems (OS X, Linux, Windows).

Thanks again.

[Andrew Nayenko]

Hi,

> Just wanted to drop you a note that all is going very well with using
> exfat on all three operating systems (OS X, Linux, Windows).

Good to know, thanks.

BTW I discovered that Mac OS X solves access right issue for FAT32 by
setting UID and GID, not umask. So it may be more accurate to mount
using a command like this:
$ sudo mount.exfat-fuse /dev/disk4s1 /mnt/jim-freeagent -o uid=`id
-u`,gid=`id -g`
For this reason I decided not to make umask=0 the default.

--
Andrew Nayenko <res...@gmail.com>