Date: Fri, 9 Aug 2019 07:42:35 -0600 From: Alan Somers <asomers@freebsd.org> To: gljennjohn@gmail.com Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: FUSE Call for Testing Message-ID: <CAOtMX2ikJAuxAfu1R6nOLOyT7n0t=gvN0j-fbnykpcOGuo-Yaw@mail.gmail.com> In-Reply-To: <20190809153806.1e550fa9@ernst.home> References: <CAOtMX2iynQJoY104oEyvizPxHXG1f9FCD48YHnXgSYsKT7Ot_A@mail.gmail.com> <20190809110236.07d33c93@ernst.home> <CAOtMX2jp6UPSbYBWHYe3kSQJUvjrqn-wd1Cuy%2Bbs%2BvP8FhfM6Q@mail.gmail.com> <20190809153806.1e550fa9@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 9, 2019 at 7:38 AM Gary Jennejohn <gljennjohn@gmail.com> wrote: > > On Fri, 9 Aug 2019 06:49:36 -0600 > Alan Somers <asomers@freebsd.org> wrote: > > [snip test results] > > > Thanks for the report, Gary. BTW, fusefs mounts are only > > interruptible when mounted with "-o intr". If you didn't use that > > option, then the signal would only interrupt cp after the write to > > fusefs was done. Also, not every fuse file system supports > > interrupts. Looking through its sources, I don't think that > > fusefs-ntfs does. > > > > I'm not convinced of that. I interrupted the 5.2GiB transfer > several times to try out different UBLIO environment settings > and it stopped pretty much immediately. I also did not use > mount but rather a direct invocation of ntfs-3g. > > I suspect that ntfs-3g stops after the interrupt once it has > flushed the UBLIO buffers. > > -- > Gary Jennejohn (gj@) Well, I can guarantee that the write(2) into fusefs was not interrupted if you did not specify "-o intr". I know, because I wrote that code. You would need to use "-o intr" whether you mount by invoking mount or ntfs-3g. But cp probably only copies a few KB to a few hundred KB at a time. So even without "-o intr", a signal would probably feel fairly responsive. -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2ikJAuxAfu1R6nOLOyT7n0t=gvN0j-fbnykpcOGuo-Yaw>