Date: Fri, 9 Aug 2019 15:43:44 +0200 From: Gary Jennejohn <gljennjohn@gmail.com> To: Alan Somers <asomers@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: FUSE Call for Testing Message-ID: <20190809154344.0fb9a92c@ernst.home> 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, 9 Aug 2019 15:38:06 +0200 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. > Upon reconsideration, I guess you're right. What stopped was cp and not necessarily ntfs-3g. Still, ^C did what I expected. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190809154344.0fb9a92c>