Date: Fri, 26 Oct 2007 16:14:26 -0500 From: Novembre <novembre@gmail.com> To: "Alejandro Pulver" <alepulver@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: NTFS-3G mount during boot Message-ID: <3b47caa90710261414v4415ef75wc865399fa7237fe2@mail.gmail.com> In-Reply-To: <20071025211222.52d78a0d@deimos.mars.bsd> References: <3b47caa90710062301s32d54e30j1f2e64eb65126879@mail.gmail.com> <20071025211222.52d78a0d@deimos.mars.bsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/25/07, Alejandro Pulver <alepulver@freebsd.org> wrote: > On Sun, 7 Oct 2007 01:01:33 -0500 > Novembre <novembre@gmail.com> wrote: > > > Hi, > > > > 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 which 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 the > > 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%fragmentation) > > /dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS > > /dev/ad0s2d: clean, 14076698 free (314 frags, 1759548 blocks, 0.0%fragmentation) > > 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/ad0s2a > > 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=/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? > > > > 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 > > Thanks a lot for your patches and notice. I didn't CC you since I was thinking that I'm doing something wrong myself (I'm still not very experienced in FreeBSD). One thing I didn't quite get is that do I have to wait for fusefs-kmod to be updated as well before going on to upgrade NTFS-3G?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3b47caa90710261414v4415ef75wc865399fa7237fe2>