Date: Thu, 25 Oct 2007 21:12:22 -0300 From: Alejandro Pulver <alepulver@FreeBSD.org> To: Novembre <novembre@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: NTFS-3G mount during boot Message-ID: <20071025211222.52d78a0d@deimos.mars.bsd> In-Reply-To: <3b47caa90710062301s32d54e30j1f2e64eb65126879@mail.gmail.com> References: <3b47caa90710062301s32d54e30j1f2e64eb65126879@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/xXvl8ZYcO7B9vPB3Zgj16tN Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 7 Oct 2007 01:01:33 -0500 Novembre <novembre@gmail.com> wrote: > Hi, >=20 Hello. I have fixed the problem together with the NTFS-3G 1.1004 update. A part of the fix involves fusefs-kmod and needs maintainer approval, but is trivial. See below for the details. > The ongoing problem with mounting my NTFS partition at boot time still > remains. I have upgraded ntfs-3g to the latest version from ports: > ---------- > [user@pasargadae ~]$ pkg_info | grep fuse > fusefs-kmod-0.3.9.p1 Kernel module for fuse > fusefs-libs-2.7.0_1 FUSE allows filesystem implementation in userspace > fusefs-ntfs-1.913 Mount NTFS partitions (read/write) and disk images > [user@pasargadae ~]$ pkg_info | grep libublio > libublio-20070103 User space caching library > ---------- > According to the fusefs-ntfs Makefile revision 1.19 (the current one whic= h I > have installed is revision 1.20), a symlink to /usr/local/bin/ntfs-3g is > placed in /usr/sbin/mount_ntfs-3g to allow using with 'mount -t ntfs-3g' = and > in /etc/fstab, after mounting /usr. So my current /etc/fstab looks like t= he > following: > ---------- > [user@pasargadae ~]$ cat /etc/fstab > # Device Mountpoint FStype Options Dump > Pass# > /dev/ad0s2b none swap sw 0 0 > /dev/ad0s2a / ufs rw 1 1 > /dev/ad0s2d /home ufs rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > /dev/ad0s1 /mnt/windows ntfs-3g rw 0 0 > ---------- > However, when I boot the system, I get the following errors: > ---------- > [user@pasargadae ~]$ dmesg -a > ... > swapon: adding /dev/ad0s2b as swap device > Starting file system checks: > /dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad0s2a: clean, 2720732 free (22356 frags, 337297 blocks, 0.6%fragmen= tation) > /dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad0s2d: clean, 14076698 free (314 frags, 1759548 blocks, 0.0%fragmen= tation) > Mounting local file systems: > fuse: failed to open fuse device: No such file or directory > ... This is because fuse.ko is not loaded at the time. The Linux version loads the module if required, but I didn't find patching it for FreeBSD needed because of the rc.d script (here the problem is about ordering, see below). It can be solved by adding the "late" option in /etc/fstab, so it will only try in the second one (which leads to the other problem). I've added this information to pkg-message. > Starting fusefs. > fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > ... > Mounting late file systems: > fuse: failed to exec mount program: No such file or directory > ---------- This is because mount_fusefs is in /usr/local/sbin and is not in the search path of fusefs-ntfs (at that time). A patch is waiting for approval, in the meantime create the symlink manually: # ln -s /usr/local/sbin/mount_fusefs /usr/sbin > The first error above is because the fuse kernel module is not yet loaded. > However, I don't understand the second error from "Mounting late file > systems" though. Does it show that the symlink is not doing its job? This= is > from /var/log/messages which shows that ntfs-3g has been run: > ---------- > Oct 6 14:22:40 pasargadae kernel: Trying to mount root from ufs:/dev/ad0= s2a > Oct 6 14:22:45 pasargadae kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI > 7.8 > Oct 6 14:22:45 pasargadae ntfs-3g[811]: Version 1.913 > Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mounted /dev/ad0s1 (Read-Write, > label "", NTFS 3.0) > Oct 6 14:22:45 pasargadae ntfs-3g[811]: Cmdline options: (null) > Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mount options: > noatime,silent,allow_other,fsname=3D/dev/ad0s1 > ---------- > which can be confirmed by noting that /dev/fuse0 has been created in /dev/ > and that 'ps -ax' shows > ---------- > 811 ?? Is 0:00.00 mount_ntfs-3g /dev/ad0s1 /mnt/windows (ntfs-3g) > ---------- > Despite all this, my NTFS partition is not mounted. Does anybody know of a > solution for this? >=20 It seems NTFS-3G is not prepared for the case where mount_fusefs wasn't found, that's why it behaves strangely in this case. BTW, the next time please CC me too so I can work on the problem early. Best Regards, Ale --Sig_/xXvl8ZYcO7B9vPB3Zgj16tN Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHITDniV05EpRcP2ERAkl8AJ9/6ue4VDBY+qWmVcHS2fKTaSn1qwCglkVS qrL9SayJ95B7+i8gEaI8S5Q= =v5xO -----END PGP SIGNATURE----- --Sig_/xXvl8ZYcO7B9vPB3Zgj16tN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071025211222.52d78a0d>