On Tue, 2008-03-11 at 17:30 +0100, Mark Phalan wrote:
> On Tue, 2008-03-11 at 09:21 -0700, Mathis Kloo?? wrote:
> > > truss -t mount ntfs-3g ...
> >
> > # truss -t mount ntfs-3g /dev/dsk/c0d1p1 /mnt/1
> > mount("/devices/pci at 0", "/mnt/1", MS_NOSUID|MS_OPTIONSTR, "fuseblk",
> > 0x00000000, 0, 0x0808D7D8, 1024) Err#22 EINVAL
> > fuse: mount failed: invalid argument
>
> Well at least one problem there is "fuseblk". I'll take a look.
Sorry for the delay in getting back to you...
Try running ntfs-3g like this:
???mount ntfs-3g /dev/rdsk/c0d1p1 /mnt/1
(Note the 'rdsk' in place of 'dsk').
Calling ntfs-3g like this causes ntfs-3g to use the 'fuse' filesystem
type rather than the 'fuseblk' one (which we don't currently support).
The 'fuseblk' filesystem provides for some extra features not available
with the regular 'fuse' filesystem. It's only used for block devices
(hence the 'blk') and does device locking, allows multiple mounts and
probably other stuff I don't know about. This is something we should try
to support in the future.
-Mark
