Date: Wed, 24 Jul 2013 17:22:16 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Kevin Oberman <rkoberman@gmail.com> Cc: Alexander Panyushkin <vsityz@gmail.com>, Pedro Giffuni <pfg@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FUSE not work. Message-ID: <20130724152216.GE63694@ithaqua.etoilebsd.net> In-Reply-To: <CAN6yY1tC0n=jijX2kGJrZu2Pc45%2BhaQsHFrEsozkucT%2BTZL-NA@mail.gmail.com> References: <51E94F09.4020109@FreeBSD.org> <51E95B4D.4030104@gmail.com> <51E96C84.3000209@FreeBSD.org> <51E97265.8040507@gmail.com> <51E9E669.3090500@FreeBSD.org> <CAN6yY1tC0n=jijX2kGJrZu2Pc45%2BhaQsHFrEsozkucT%2BTZL-NA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Q8BnQc91gJZX4vDc Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 19, 2013 at 09:42:41PM -0700, Kevin Oberman wrote: > On Fri, Jul 19, 2013 at 6:22 PM, Pedro Giffuni <pfg@freebsd.org> wrote: >=20 > > On 19.07.2013 12:07, Alexander Panyushkin wrote: > > > >> 19.07.2013 19:42, Pedro Giffuni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> > >>> (re-posting since the original response didn't make it through) > >>> > >>> On 19.07.2013 10:29, Alexander Panyushkin wrote: > >>> > >>>> 19.07.2013 17:36, Pedro Giffuni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >>>> > >>>>> Hello; > >>>>> > >>>>> The internal data structures in the FUSE kernel module have been > >>>>> updated to be more compatible with MacFUSE and the linux FUSE. > >>>>> > >>>>> This basically means you have to rebuild your fuse modules > >>>>> (including NTFS). > >>>>> > >>>>> We should not really update the FUSE_KERNEL_MINOR_VERSION yet. > >>>>> I will add a note to UPDATING. > >>>>> > >>>>> Pedro. > >>>>> > >>>> > >>>> > >>>> > >>>> Unfortunately the port is not build in FreeBSD 10 > >>>> > >>>> > >>>> =3D=3D=3D>>> Starting build for sysutils/fusefs-kmod <<<=3D=3D=3D > >>>> > >>>> > >>> fusefs-kmod is not needed on -current. I meant you have to rebuild > >>> and reinstall fusefs-* ; in particular fusesfs-libs and ntfs. > >>> > >>> Since this is a ports issue I will not update the UPDATING file. > >>> > >>> Developers that need to know should use __FreeBSD_version > >>> 1000038 as a reference. > >>> > >>> > >> I rebuild sysutils/fusefs-ntfs with Clang and GCC, but this has no eff= ect. > >> > >> sysctl kern.osreldate > >> kern.osreldate: 1000037 > >> > >> ntfs-3g /dev/ad10s1 /mnt/ntfs_0 > >> mount > >> ... > >> /dev/fuse on /mnt/ntfs_0 (fusefs, local, synchronous) > >> > >> ls -la /mnt/ntfs_0 > >> unique: 18, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 47053 > >> getattr / > >> unique: 18, success, outsize: 112 > >> fuse: writing device: Invalid argument > >> ls: /mnt/ntfs_0: Input/output error > >> > >> fuse is at least partly broken in -current. I discovered that if you > mount two devices that use fuse, when you umount any of them, ll are mark= ed > as not mounted and disappear from df(1) or mount(8) output, but only one = is > actually cleanly unmounted and, if it has been written to, will likely be > corrupt. This applies to at least ntfs. >=20 > ATM no one is supporting fuse in current, so this may become a serious > issue before long. This is fixed now. btw this problem is/was not related to fuse on current but rather to fusefs-libs. Bapt --Q8BnQc91gJZX4vDc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlHv8SgACgkQ8kTtMUmk6Ex4/gCgovd8Gwy+wIGlt80H8pnk23zk FHMAn1jmPxqM3EDKiTCTEOkXNYOfTS10 =zCmx -----END PGP SIGNATURE----- --Q8BnQc91gJZX4vDc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130724152216.GE63694>