From owner-freebsd-current@freebsd.org Fri Aug 9 13:42:50 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0BECFC9A9A for ; Fri, 9 Aug 2019 13:42:50 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 464mdh53HGz4bJC for ; Fri, 9 Aug 2019 13:42:48 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf1-f42.google.com with SMTP id c9so69508787lfh.4 for ; Fri, 09 Aug 2019 06:42:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BYc0r6DcGw9OMrioWWHnwydWbc9NqPgG5EyBw8wU2oc=; b=Tb6SEy1vEv8RJFg1q81Th5c1g2CI2J7jhOcJ1sqQ/yGLa7R9MqaYuFAxKaRln10SwJ fJtiLNjhT4e/qSm/+eXx/6NTDia3bXgx4di27y2a8CJcFBizvs0ZNtzpzUSh8PA8btjT MfW8c3DO/BM1zVmZv7T8sVWOZGoYYP+jQI3xmiyiIRZnIcXfgziCYgZ2sJ2jjfv+zoFG VbVOhUPYGa491b53dXQ3Gbtwnsm396nU9nidyUYPCGzcB22Zh1lzZVsC5uG77o7rNyOP zJ6Y0y5brzdw/nALme31AA9IRbOeps0olovKHnoEH/ppPhrTwB3uwyyozTlNrkjHiG8V Jywg== X-Gm-Message-State: APjAAAV7upGu6QghNtYmglx6rri9ZbxgZh0W/mSk9nvq7okMNxTq+doR NlA4cfxRdQ5/+Vo87pFs6y8ucUqjpTqYp1+VuMD5mok8ykQ= X-Google-Smtp-Source: APXvYqwE8GKdoDeOU7J5PNP1DeC+P96iURqdgzELIx4495vadDOseSYao5+ZBY9y2NeCHzih8IlOV5AC3tOVTLvjWM0= X-Received: by 2002:a19:7908:: with SMTP id u8mr12644678lfc.178.1565358166899; Fri, 09 Aug 2019 06:42:46 -0700 (PDT) MIME-Version: 1.0 References: <20190809110236.07d33c93@ernst.home> <20190809153806.1e550fa9@ernst.home> In-Reply-To: <20190809153806.1e550fa9@ernst.home> From: Alan Somers Date: Fri, 9 Aug 2019 07:42:35 -0600 Message-ID: Subject: Re: FUSE Call for Testing To: gljennjohn@gmail.com Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 464mdh53HGz4bJC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.167.42 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-4.29 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.997,0]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[42.167.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.29)[ip: (-0.61), ipnet: 209.85.128.0/17(-3.38), asn: 15169(-2.40), country: US(-0.05)]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2019 13:42:50 -0000 On Fri, Aug 9, 2019 at 7:38 AM Gary Jennejohn wrote: > > On Fri, 9 Aug 2019 06:49:36 -0600 > Alan Somers 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