Other NTFS question

I have NTFS questions.
1) Thread ntfs-3g-vs-mount-t-ntfs-3g.45173 I can mount NTFS USB stick via ntfs-3g /dev/da0s1 /mnt/flash and it works (read/ write), unmounts etc., but cannot via mount -t ntfs-3g /dev/da0s1 /mnt/flash.
2) I've managed to mount the stick (on the other machine) via ntfs-3g /dev/da0s1 /mnt/flash, It seemed working, I've read files, have written files and read them again. But couldn't unmount with the error "unknown filesystem". So afterwards I've discovered that there are no newly written files on the stick.

What is the right way to use such sticks? What was the problem? Should I load kernel modules? Can't find instruction in ntfs-3g manual.
 
Code:
gpart show da0
pkg install -y fusefs-ntfs
[DEL]echo 'kldload fuse' >> /etc/rc.conf[/DEL]
echo fuse_load="YES" >> /boot/loader.conf
reboot
ntfs-3g /dev/da0s1 /mnt/flash

...should get you close, although this may depend on which version of FreeBSD you are running

I meant to put a strike out tag in the above but (DEL) was inserted. Is there a tag for strikeout? I guess there is but you can't include it within CODE...
 
Code:
echo 'kldload fuse' >> /etc/rc.conf
Never put commands in rc.conf! The rc.conf file is sourced multiple times during the boot process by various rc(8) scripts. If you put commands in there they will get executed each and every time the file is sourced.

Code:
kld_list="fuse"
 
Never put commands in rc.conf! The rc.conf file is sourced multiple times during the boot process by various rc(8) scripts. If you put commands in there they will get executed each and every time the file is sourced.

Oops....

That should have been echo fuse_load="YES" >> /boot/loader.conf
 
balanga
it should not make any difference with a supported FreeBSD version.
Not everyone runs a supported version of FreeBSD.
If someone had used a program and asks questions about its usage, it makes little sense giving him command lines for it's installation. He has it installed already ;)

Not everyone who wants to mount NTFS partitions on FreeBSD will know that fuse has to be loaded. The answers on the forum are not just for OPs...
 
It is on 12-STABLE amd64.
Code:
# kldload fuse
kldload: can't load fuse: module already loaded or in kernel
So, the problem was not in kernel module.
After reboot everything went O.K. With unmount.
But there was an "unknown filesystem" error and loss of data as its consequence before.
 
You really should be on 12-RELEASE which is the production version. STABLE is a development version.
-STABLE is a supported development version, -CURRENT is a unsupported development version.
 
Why would someone use STABLE if RELEASE is available?
Because not all bug fixes are backported to a -RELEASE. Besides that -STABLE gets new features added and you would have to wait until the next -RELEASE to use them. You can simply see a -STABLE version as an alpha of the next -RELEASE version.


AIUI you can't run freebsd-update() on anything but RELEASE versions.
A source upgrade/update is always possible, freebsd-update(8) is a tool specifically made to do a binary update/upgrade of -RELEASE versions. Doing a source update/upgrade is not that hard, it just takes time. And back when I started a source update/upgrade was the only way to update.
 
Back
Top