From owner-freebsd-fs@freebsd.org Sun Aug 27 04:15:49 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FD70DE65C7 for ; Sun, 27 Aug 2017 04:15:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BDA664032 for ; Sun, 27 Aug 2017 04:15:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7R4Fm7s033417 for ; Sun, 27 Aug 2017 04:15:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 114955] [cd9660] [patch] [request] support for mask,dirmask,uid,gid for mount_cd9660(8) / CD9660 Date: Sun, 27 Aug 2017 04:15:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 6.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jpaetzel@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2017 04:15:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D114955 Josh Paetzel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |Overcome By Events CC| |jpaetzel@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Aug 27 04:34:01 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02F6BDE70D8 for ; Sun, 27 Aug 2017 04:34:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E532B64E7F for ; Sun, 27 Aug 2017 04:34:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7R4XwTq078839 for ; Sun, 27 Aug 2017 04:34:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 148368] [zfs] ZFS hanging forever on 8.1-PRERELEASE Date: Sun, 27 Aug 2017 04:33:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jpaetzel@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2017 04:34:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148368 Josh Paetzel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpaetzel@FreeBSD.org Status|In Progress |Closed Resolution|--- |Overcome By Events --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Aug 27 16:34:43 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 447A9DF30B8 for ; Sun, 27 Aug 2017 16:34:43 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 002207680A; Sun, 27 Aug 2017 16:34:42 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-it0-x243.google.com with SMTP id c196so2866112itc.3; Sun, 27 Aug 2017 09:34:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6vFvUyiu32+jKkwImaNIOQ7n4ghKvDnu8bWT9q9oUKo=; b=ZYq4HysG7nWJZUOnh1KU7OmBYi91AvMD/PY03fl42BE8WZgPa83/HRq1thsRqI+vWu tmHUj4qa7BlyFMOrnM6NIPfmoWZ3dyM+rth5yb++8gYZTEzobYzrk4O6wiTtTZZrF205 CMjaCVmIElKPzZJmm/fdFpyAbsx1KLkOKXuNqDj17QUizAiXaKvJd8m5MLdPeSnlpmN3 wJBsaSj5YZXeivrFmxyaBAt0jmUHxinCRxkUTEnwYVG3DE7x4fHQm7KHIkbCUHcsqkbL eZOwy1E+ox29vdppccMtA/zAa4/D0S7bDsYzpmXwHIKqHIsRg2ITGSLBm4flGAwQV7KW /S5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6vFvUyiu32+jKkwImaNIOQ7n4ghKvDnu8bWT9q9oUKo=; b=c76vpfnIoU7pZBU2kntx0nbEvs03hu+qorBI5G9smklUw4C4FRf0NkFcYLs0wsa8UP KVahlZaknrrwqgXeQWUrjFH3Xw5P8A+y2W/0Fv4UNv7LaSh5Vw7rCSK+h6QIX6ScgUcT 50ngcNs561g/cQsy+/HAAjL6W+kHm9nTuCGr/Z8B4od3uf2+llHmsjKec7yRKnzTi77p Cb+huJjf/eU003FG58JB3kd2P2PqI477LTbjM/mVAm+nk4nrapSYQfdQOg2Cvi6KOuNm 1xq1VE4j9emqKF359HT4kRVsefWarypjri/8oWAAyQsqkg0dz1hK4sBpxdJDFd+EKNZ5 5M4g== X-Gm-Message-State: AHYfb5iGX/vwLzaTtYadaCnYD0gupUsRn51Bjs+BeCnurpqqpV2JfS6Y vzBmpka5Pj8JQJMLaEeP9BKsYz3OJQ== X-Received: by 10.36.149.197 with SMTP id m188mr681337itd.112.1503851682164; Sun, 27 Aug 2017 09:34:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.22.66 with HTTP; Sun, 27 Aug 2017 09:34:41 -0700 (PDT) In-Reply-To: <201708250251.v7P2pwcl029687@chez.mckusick.com> References: <201708250251.v7P2pwcl029687@chez.mckusick.com> From: Aijaz Baig Date: Sun, 27 Aug 2017 22:04:41 +0530 Message-ID: Subject: Re: Tips on remote debugging for filesystem code To: Kirk McKusick Cc: jhb@freebsd.org, Julian Elischer , freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2017 16:34:43 -0000 Thanks for the heads up Kirk. Unfortunately I just ran into a roadblock with Bhyve since I am running FreeBSD on core2duo which "officially" doesn't support Bhyve yet. Is there some other way I can get this to work? I have installed FreeBSD bare metal now if it helps. On Fri, Aug 25, 2017 at 8:21 AM, Kirk McKusick wrote: > > From: Aijaz Baig > > Date: Fri, 25 Aug 2017 06:33:25 +0530 > > Subject: Re: Tips on remote debugging for filesystem code > > To: Kirk McKusick > > Cc: Julian Elischer , freebsd-fs@freebsd.org > > X-ASK-Info: Message Queued (2017/08/24 18:09:30) > > X-ASK-Info: Confirmed by User (2017/08/24 18:40:26) > > > > On Fri, Aug 25, 2017 at 12:00 AM, Kirk McKusick > wrote: > > > >>> To: Aijaz Baig , freebsd-fs@freebsd.org > >>> Subject: Re: Tips on remote debugging for filesystem code > >>> From: Julian Elischer > >>> Date: Thu, 24 Aug 2017 16:24:50 +0800 > >>> > >>> On 24/8/17 1:40 pm, Aijaz Baig wrote: > >>> > >>>> ... > >>>> How do you guys normally do it? Keen to hear tips and best practices > >>> > >>> I have had more success recently using BHype to make a Virtual FreeBSD > >>> machine and connecting to it using the built-in gdb interface. > >>> > >>> Firstly it is easier than a serial interface and secondly you don't > >>> need two machines. > >> > >> Is there documentation that describes how to do this? I have been using > >> a patched up set of scripts provided by John Baldwin a couple of years > >> ago to use kgdb with a bhyve VM. But if there is an existing way to do > >> it now, I would rather switch to it. > >> > >> Kirk McKusick > > > > Yes please I would love to hear about this as well. Nonetheless if > > any one of you Kirk or Julian could help me get started a bit with > > what how you guys use it (and those scripts that Kirk talks about), > > it would be really nice. > > Below I enclose an email from John Baldwin that got me going on > debugging under bhyve. I am copying John as he likely has progressed > considerably in the last two years, so can likely provide some more > up to date tips. Though as far as I can see, he never added his > updates to the bhyve/vmrun.sh script. So I am not sure how Julian > has set up his bhyve debugging which is what lead to my initial question. > > > By the way is this bhyve the only way to go for fs code debugging? > > > > Best Regards, > > Aijaz Baig > > You could use multiple machines or run under other hypervisors, but > bhyve lets you do everything on one machine and has the benefit of > easily integrating with kgdb. > > Another option is to read the several chapters in my book that describes > how the VFS layer works ;-) > > Kirk McKusick > > =-=-= > > From: John Baldwin > Date: Tue, 08 Sep 2015 16:53:26 -0700 > To: Kirk McKusick > Subject: Re: kgdb ported to devel/gdb > > On Tuesday, September 08, 2015 04:05:06 PM Kirk McKusick wrote: > >> From: John Baldwin > >> To: freebsd-current@freebsd.org > >> Subject: kgdb ported to devel/gdb > >> Date: Mon, 31 Aug 2015 14:32:04 -0700 > >> > >> Over the past several months I have ported kgdb to the version of > >> gdb in ports. I have a pending patch to the gdb port to add fork > >> following, but once that is done (and possibly after updating to > >> 7.10) I will try to add my existing work as a KGDB option on the > >> port. Until such time, you can try the newer kgdb by checking out > >> my branch from git. > >> > >> Here's my cheat sheet on how to build the newer kgdb. Note that > >> if you build a world with my cross-libkvm patches you should get a > >> kgdb that can debug i386 cores on amd64 and vice versa. > >> > >> All of the targets that the native devel/gdb support have their > >> backends ported (so x86, sparc64, powerpc and powerpc64). I have > >> not yet ported arm or mips since those don't work for userland yet > >> in upstream gdb. I have only compiled non-x86 backends. Testing > >> of the new kgdb on sparc64 and powerpc would be appreciated. > >> > >> Steps: > >> > >> % git clone https://github.com/bsdjhb/gdb.git > >> % git checkout freebsd-7.9.1-kgdb > >> % fetch http://www.freebsd.org/~jhb/gdb/build > >> % pkg install devel/gdb > >> > >> # Having gdb installed will mean you get the python bindings in the > right > >> # place. > >> > >> % pkg install gmake > >> > >> # I think this is the only build tool you need? > >> > >> % ./build > >> % cd obj > >> > >> # Replace 'obj' with 'obj.' for all but amd64 > >> > >> % gmake > >> > >> # ... wait > >> > >> You will now have a binary at 'obj/gdb/kgdb'. I just run it from my obj > >> tree currently when testing. Once it becomes part of the port it will > get > >> installed as /usr/local/bin/kgdb791 or some such. > > > > This is very helpful, thanks for doing it. > > > > I recently dumped my (very ancient) i386 debugging machine and started > > debugging in a bhyve virtual machine. Much quicker to boot and test. > > But, I lost the ability to remote debug over a serial line. Is there > > some way to remote attach to my virtual machine so I can once again > > set breakpoints, single step it, etc? > > Yes, I do this with my VMs (and this is how I tested the i386 <--> amd64 > cross debugging). The way I do this is to attach a nmdm device to COM2 > (uart1) in my VMs and then run gdb over that. First, I use a patched > vmrun.sh > to always create a /dev/nmdm2{A,B} pair of devices attached to COM2 > on each VM. The 'B' device is used by bhyve, and I use the 'A' device on > the > host with 'target remote' in kgdb. My change to vmrun.sh is this: > > --- /usr/share/examples/bhyve/vmrun.sh 2015-08-15 16:31:57.891092000 > -0700 > +++ bhyve/vmrun.sh 2015-09-08 16:46:05.000000000 -0700 > @@ -91,9 +91,13 @@ > loader_opt="" > bhyverun_opt="-H -A -P" > pass_total=0 > +com2="" > > -while getopts ac:C:d:e:g:hH:iI:m:p:t: c ; do > +while getopts 2:ac:C:d:e:g:hH:iI:m:p:t: c ; do > case $c in > + 2) > + com2=${OPTARG} > + ;; > a) > bhyverun_opt="${bhyverun_opt} -a" > ;; > @@ -269,7 +273,13 @@ > i=$(($i + 1)) > done > > + if [ -n "${com2}" ]; then > + devargs="$devargs -l com2,${com2}" > + elif kldstat -qm nmdm; then > + devargs="$devargs -l com2,/dev/nmdm${vmname}2B" > + fi > + > ${FBSDRUN} -c ${cpus} -m ${memsize} ${bhyverun_opt} \ > -g ${gdbport} \ > -s 0:0,hostbridge \ > -s 1:0,lpc \ > > Note that if you have nmdm kldloaded, this version will place a nmdm > device on COM2 automatically. > > Next, I enable gdb on COM2 by adding 'hint.uart.1.flags="0x80"' to > /boot/device.hints inside the VM. > > To test it, I boot the VM and then run 'sysctl debug.kdb.enter=1' on the > console (or over an ssh session). On the host I run my new kgdb (since > it can do i386 cross debugging via remote out of the box). Note that > you will need the kernel.debug on the host. I do this by keeping my > work tree on my host machine and exporting it via NFS into the guest. > I then build the kernel the "old" way using config and make directly so > that the kernel.debug is at 'sys/i386/compile//kernel.debug'. You > can then run the new kgdb as 'kgdb /path/to/kernel.debug'. In the VM > console, run 'gdb' at the db> prompt to switch over to GDB. You can then > use 'target remote /dev/nmdm2A' to connect to it. For example, > if your VM is named vm0, you would use /dev/nmdmvm02A. > > -- > John Baldwin > -- Best Regards, Aijaz Baig From owner-freebsd-fs@freebsd.org Sun Aug 27 19:04:07 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5BF2DF61EE for ; Sun, 27 Aug 2017 19:04:07 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [70.36.157.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 83CDB7F88F for ; Sun, 27 Aug 2017 19:04:07 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (localhost [IPv6:::1]) by chez.mckusick.com (8.15.2/8.15.2) with ESMTP id v7RJ7h18017535; Sun, 27 Aug 2017 12:07:43 -0700 (PDT) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201708271907.v7RJ7h18017535@chez.mckusick.com> From: Kirk McKusick To: Aijaz Baig Subject: Re: Tips on remote debugging for filesystem code cc: freebsd-fs@freebsd.org In-reply-to: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17533.1503860863.1@chez.mckusick.com> Content-Transfer-Encoding: quoted-printable Date: Sun, 27 Aug 2017 12:07:43 -0700 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2017 19:04:07 -0000 > From: Aijaz Baig > Date: Sun, 27 Aug 2017 22:04:41 +0530 > Subject: Re: Tips on remote debugging for filesystem code > To: Kirk McKusick > = > Thanks for the heads up Kirk. Unfortunately I just ran into a roadblock > with Bhyve since I am running FreeBSD on core2duo which "officially" > doesn't support Bhyve yet. > = > Is there some other way I can get this to work? I have installed FreeBSD > bare metal now if it helps. Best solution is to get some hardware that can run bhyve :-) Absent that, you can revert to the historic method of remote debugging over serial lines, see chapter 10 of the FreeBSD handbook. More specifically: https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-onlin= e-gdb.html Kirk McKusick From owner-freebsd-fs@freebsd.org Sun Aug 27 19:51:32 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29F65DF7071 for ; Sun, 27 Aug 2017 19:51:32 +0000 (UTC) (envelope-from joris.dedieu@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4E2980D16 for ; Sun, 27 Aug 2017 19:51:31 +0000 (UTC) (envelope-from joris.dedieu@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id g33so10685343ioj.3 for ; Sun, 27 Aug 2017 12:51:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=TNbL6U+4/5zG4TgCFUw6FSSUanmA//1C/r1oD5CJ+Js=; b=GoZdrAhXgqjzb+CZiVJxvqXc1SKD1BFq4oRyYVaL1ojIs73uIzSVQ/iLSdILlje7sd uxq1U6ROCU9pgpQaGmo/eoYp2yH4NGrhZEP6fSDi7YzweRYuVHSOaWIW1QQ01WGzERUE Jti9yKUHyh/3AJDs2C3I0W63o3D75+pCNJCOuhLqZJHuWpio/j3d/Sv3Cac6iBw/KtmT 05aTxFvdIejnWAaB7OPLJRlZCR/oAmc1yG5LWrg3ExF2LTG1hiJ4PwwhDT3dInp6w7CE 4Db09O/XB0TlevUOp3zJPdp1Pz8x9EzR01Rtx/jOOFoDbUbVF7811bHETX7E9YAE3rOa Qahw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=TNbL6U+4/5zG4TgCFUw6FSSUanmA//1C/r1oD5CJ+Js=; b=aoTVrlx+PrWvjCDWo1c2k9iLcjRddX1v9dxDJw1MdGF/sCykR7+R/AsR0i4jMHsnAZ a0TIVYpYZ7WzVfvueyyAuHIP2e/Ka67prPSgUvJMtP1yKLoEVN/uB5hRQwgl+4R4/UgY 5Dk4CSci25Ivr/grJZCnVquBE7Kv46OR5XbChclICTms7bV2b7S5EMmtFYO18o+8eVeN IlbAvjC/iGTgwl2IU2lYiuFNYwkM+3hVgMRsZHj/FLJTLwsFSAu1BOJKDAkMEI+nzTR5 5uug0aAROKNV25yCRr+v9sLffyEqTHVozkOvW3+2Lc3tsHZkpr/EZ71zzyqy+9B4xFKR md5w== X-Gm-Message-State: AHYfb5gwH0QwwcVjih6BKzfhStUWX09zfrL1GrGIE71JQQKNHjdQpGc9 rxfbMYsnoM5avAxqJhW0h20XF+iqK9Iv X-Received: by 10.107.142.22 with SMTP id q22mr5031015iod.109.1503863490927; Sun, 27 Aug 2017 12:51:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.146.3 with HTTP; Sun, 27 Aug 2017 12:51:29 -0700 (PDT) Received: by 10.79.146.3 with HTTP; Sun, 27 Aug 2017 12:51:29 -0700 (PDT) In-Reply-To: <201708271907.v7RJ7h18017535@chez.mckusick.com> References: <201708271907.v7RJ7h18017535@chez.mckusick.com> From: joris dedieu Date: Sun, 27 Aug 2017 21:51:29 +0200 Message-ID: Subject: Re: Tips on remote debugging for filesystem code To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2017 19:51:32 -0000 Le 27 ao=C3=BBt 2017 9:04 PM, "Kirk McKusick" a =C3= =A9crit : > > > From: Aijaz Baig > > Date: Sun, 27 Aug 2017 22:04:41 +0530 > > Subject: Re: Tips on remote debugging for filesystem code > > To: Kirk McKusick > > > > Thanks for the heads up Kirk. Unfortunately I just ran into a roadblock > > with Bhyve since I am running FreeBSD on core2duo which "officially" > > doesn't support Bhyve yet. > > > > Is there some other way I can get this to work? I have installed FreeBS= D > > bare metal now if it helps. > > Best solution is to get some hardware that can run bhyve :-) > > Absent that, you can revert to the historic method of remote > debugging over serial lines, see chapter 10 of the FreeBSD > handbook. More specifically: > > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online= -gdb.html > You can also run freebsd with qemu which permit serial over tcp. Joris > Kirk McKusick > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Sun Aug 27 19:58:52 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D80DADF72C0 for ; Sun, 27 Aug 2017 19:58:52 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [173.228.5.8]) by mx1.freebsd.org (Postfix) with ESMTP id C305180EFE for ; Sun, 27 Aug 2017 19:58:52 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 49400124AE9F; Sun, 27 Aug 2017 12:54:28 -0700 (PDT) To: Aijaz Baig cc: freebsd-fs@freebsd.org Subject: Re: Tips on remote debugging for filesystem code In-reply-to: Your message of "Sun, 27 Aug 2017 22:04:41 +0530." References: <201708250251.v7P2pwcl029687@chez.mckusick.com> Comments: In-reply-to Aijaz Baig message dated "Sun, 27 Aug 2017 22:04:41 +0530." Date: Sun, 27 Aug 2017 12:54:28 -0700 From: Bakul Shah Message-Id: <20170827195428.49400124AE9F@mail.bitblocks.com> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2017 19:58:53 -0000 On Sun, 27 Aug 2017 22:04:41 +0530 Aijaz Baig wrote: > Thanks for the heads up Kirk. Unfortunately I just ran into a roadblock > with Bhyve since I am running FreeBSD on core2duo which "officially" > doesn't support Bhyve yet. > > Is there some other way I can get this to work? I have installed FreeBSD > bare metal now if it helps. Years ago I used to use qemu + its GDB support. It was far more convenient than debugging over a serial like. Haven't used qemu recently but it used to run on pretty much any x86 machine. I found a copy of my message online: http://maxim.int.ru/tricks/qemu.txt Also see https://wiki.freebsd.org/qemu From owner-freebsd-fs@freebsd.org Mon Aug 28 07:42:10 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8587E07F9E for ; Mon, 28 Aug 2017 07:42:10 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 673866CC49; Mon, 28 Aug 2017 07:42:10 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-it0-x22e.google.com with SMTP id f1so13618391ith.0; Mon, 28 Aug 2017 00:42:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fgMWhxhpCgOFwuVpvllwNGoFR6aYFC5jjNIZk42EER8=; b=Qok/43SP7wZhojxt7Av/dZtHIjuPNh8OokIRWQdBY6ic2L6J62OSpfT7ZA1ur2ZcJb 6x0Vykrm72IfAK130cPngf8XnieEk1kb3cG0fNkrQYpLXwHDc0Xl1+o71fdYQp5j3DPP 7ctqhyeURToI7h4O59ZDydzYPUJV6N0wVYMg9mwwCiAaE3X32VY1w0g3o7fKoxYl8Fl/ Ui2kX40JITHSMf1xtSFJMizOO4gTNuCBngCP09KZUS81fpXCNoa3cmHTvMbgM7+EW8hm 7ThORLM4AbT0IuUllc6nL2sgqyn9GyCpPl+IkFovoQcsbJYy/PVbwdEGaOWiB+LMAbTI AHtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fgMWhxhpCgOFwuVpvllwNGoFR6aYFC5jjNIZk42EER8=; b=VD4AXgRrf07ikIzjV6/jp2M3GRvqxF755mHnqcKXT2vuG5G27l25p7D9roJAnGmVL/ AbEs+qiXUjPO+Zr3qwS+oDOdbuznBnO8bu7TJ5Vl1pS7YHK7BfzQ9jjl4DC1Pii0jSdW np+w2cpb7ItObZBUvKdp92YVSI9ZB6N+2wO6rl36ImJJELysyBz157ARIpw9cdsHCG6y rz/U3HwP/hck28Rnvt4zzYqlkfND2kPc53MFrpVA9PYt3ZoputU4tJJY5u6c2KwQyeJg Y9RT4zo2c42oMpji6cgrTegRBi7iuFlm6PCo6jthheZ57RxqH0szITJtt3wE/kVQSMh5 TWlw== X-Gm-Message-State: AHYfb5j2bwUfWtPcR23cX/IvObjejJMaA0oOFSghF2h7Ol9YrJLXUBgn Qz+MBs5T6t4PdONy2w4qP4962z/asA== X-Received: by 10.36.252.69 with SMTP id b66mr6342003ith.97.1503906129613; Mon, 28 Aug 2017 00:42:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.22.66 with HTTP; Mon, 28 Aug 2017 00:42:09 -0700 (PDT) In-Reply-To: <20170827195428.49400124AE9F@mail.bitblocks.com> References: <201708250251.v7P2pwcl029687@chez.mckusick.com> <20170827195428.49400124AE9F@mail.bitblocks.com> From: Aijaz Baig Date: Mon, 28 Aug 2017 13:12:09 +0530 Message-ID: Subject: Re: Tips on remote debugging for filesystem code To: Bakul Shah , Kirk McKusick , Julian Elischer Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 07:42:10 -0000 Thanks a lot bakul. Will certain look into this Nevertheless I got hold of a PowerEdge 320 system which DOES have a POPCNT instruction which shows support for V-x support via EPT but I still get the same error there sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 2048M -t tap0 -d guest.img -i -I FreeBSD-10.3-RELEASE-amd64-bootonly.iso fbsd10 Launching virtual machine "fbsd10" ... vm_create: Device not configured dmesg: vmx_init: processor does not support VMX operation cat /var/run/dmesg.boot | grep -i popcnt Features2=0xffba2203 Features2=0xffba2203 Any ideas? On Mon, Aug 28, 2017 at 1:24 AM, Bakul Shah wrote: > On Sun, 27 Aug 2017 22:04:41 +0530 Aijaz Baig > wrote: > > Thanks for the heads up Kirk. Unfortunately I just ran into a roadblock > > with Bhyve since I am running FreeBSD on core2duo which "officially" > > doesn't support Bhyve yet. > > > > Is there some other way I can get this to work? I have installed FreeBSD > > bare metal now if it helps. > > Years ago I used to use qemu + its GDB support. It was far > more convenient than debugging over a serial like. Haven't > used qemu recently but it used to run on pretty much any x86 > machine. I found a copy of my message online: > > http://maxim.int.ru/tricks/qemu.txt > > Also see > > https://wiki.freebsd.org/qemu > -- Best Regards, Aijaz Baig From owner-freebsd-fs@freebsd.org Mon Aug 28 13:26:50 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F481E0D6EA for ; Mon, 28 Aug 2017 13:26:50 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D039777253; Mon, 28 Aug 2017 13:26:49 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dmK3z-000LnV-9n; Mon, 28 Aug 2017 14:26:47 +0100 Date: Mon, 28 Aug 2017 14:26:47 +0100 From: Gary Palmer To: Aijaz Baig Cc: Bakul Shah , Kirk McKusick , Julian Elischer , freebsd-fs@freebsd.org Subject: Re: Tips on remote debugging for filesystem code Message-ID: <20170828132647.GA60563@in-addr.com> References: <201708250251.v7P2pwcl029687@chez.mckusick.com> <20170827195428.49400124AE9F@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 13:26:50 -0000 On Mon, Aug 28, 2017 at 01:12:09PM +0530, Aijaz Baig wrote: > Thanks a lot bakul. Will certain look into this > > Nevertheless I got hold of a PowerEdge 320 system which DOES have a POPCNT > instruction which shows support for V-x support via EPT but I still get the > same error there > > sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 2048M -t tap0 -d guest.img -i > -I FreeBSD-10.3-RELEASE-amd64-bootonly.iso fbsd10 > Launching virtual machine "fbsd10" ... > vm_create: Device not configured > > dmesg: > vmx_init: processor does not support VMX operation > > cat /var/run/dmesg.boot | grep -i popcnt > > Features2=0xffba2203 > > Features2=0xffba2203 > > Any ideas? Hi, Check the BIOS for virtualisation or other related options. Some BIOSes have the ability to turn those features off, even if the processor normally supports them Regards, Gary From owner-freebsd-fs@freebsd.org Mon Aug 28 13:33:07 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB812E0DAB5 for ; Mon, 28 Aug 2017 13:33:07 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 718A177722; Mon, 28 Aug 2017 13:33:07 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-it0-x22d.google.com with SMTP id 77so2323829itj.1; Mon, 28 Aug 2017 06:33:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qSttbieYorehVWnygdlT4aXbK0oj4CNy0ohAs1QKEaw=; b=VSOZzyOX9UCQgnASUKWq/2zhwJ6pF3tfYDaLi55iPS02wj88yZ78qbRf7gXLF5LRow G287idawwvuRIso1Iqb4GkwBOgudjaZHP4DK0jNKrg0X9FfRCI/xgbYIokhioPiSoa30 g/Vho4cZVl28E7rp6b/iFt+c58XMwNzGSSaOfiJ+XuxD54duw8q8T4roaJQGiTuridEa fgXEpqx2AqCmPji+/bHdgQXCg/q0ygCwNDNmIe1jGRTBb+kFanTVPm97hGg5pAzgAYaU ML6KVS32yaLZHQYxd3vPlPQfIFw/U8c270iyLovBEHY6OznH0UFFcgyp5PJZyT+JPfaA CwKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qSttbieYorehVWnygdlT4aXbK0oj4CNy0ohAs1QKEaw=; b=pKDr/0cWPoVAZw8ZST6wzR0EQYHXwNG5SCFAoQrSiaH6PTWpCAeeeHhUqe6Lfl7LbS /1iOCyMoTHSBFkfGp1Al5Z+7FVsm7EE0TsfkenlAPpfQXy9VCvGX8F4zGuwgC7+pNjAw fATKbKV8YE3kzFXQk5f5PskAiNlmXekygv0HFkNIVGD2wxffQ1y9fBtDBLRk4rAMiCl1 /xOHOqx13PZ5wAfNjqIgpAzGKFVejtIWGd6h+w9ZObDVfC6rna4niBDV68iAiFivLjHq AnMMwHi150ZGCELsYUHEEKlFexdxJAbpZL+Z1H3oSK5BkYgnWi1fJhFDG/9SLcaO1kTA KPcw== X-Gm-Message-State: AHYfb5htuju0I4XqxJxo7dQqBxjtWoUG6EvBt/UGdYhcxhntSCck2XlN hYAN54d6u/q2eqlYAYWL1Z8fMP2W51hP X-Received: by 10.36.79.11 with SMTP id c11mr548037itb.112.1503927186579; Mon, 28 Aug 2017 06:33:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.22.66 with HTTP; Mon, 28 Aug 2017 06:33:06 -0700 (PDT) In-Reply-To: <20170828132647.GA60563@in-addr.com> References: <201708250251.v7P2pwcl029687@chez.mckusick.com> <20170827195428.49400124AE9F@mail.bitblocks.com> <20170828132647.GA60563@in-addr.com> From: Aijaz Baig Date: Mon, 28 Aug 2017 19:03:06 +0530 Message-ID: Subject: Re: Tips on remote debugging for filesystem code To: Gary Palmer Cc: Bakul Shah , Kirk McKusick , Julian Elischer , freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 13:33:07 -0000 HI Gary Just checked that. Indeed that was the case. In addition I was running FreeBSD on top of vmware hypervisor and had not allowed hardware acceleration features pass through to the FreeBSD VM. It is now working! Need to explore more on getting it to connect to GDB Perhaps you'll see a thread soon for it (Has anything worked perfectly for the first time ever?? ;) )! On Mon, Aug 28, 2017 at 6:56 PM, Gary Palmer wrote: > On Mon, Aug 28, 2017 at 01:12:09PM +0530, Aijaz Baig wrote: > > Thanks a lot bakul. Will certain look into this > > > > Nevertheless I got hold of a PowerEdge 320 system which DOES have a > POPCNT > > instruction which shows support for V-x support via EPT but I still get > the > > same error there > > > > sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 2048M -t tap0 -d > guest.img -i > > -I FreeBSD-10.3-RELEASE-amd64-bootonly.iso fbsd10 > > Launching virtual machine "fbsd10" ... > > vm_create: Device not configured > > > > dmesg: > > vmx_init: processor does not support VMX operation > > > > cat /var/run/dmesg.boot | grep -i popcnt > > > > Features2=0xffba2203 SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> > > > > Features2=0xffba2203 SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> > > > > Any ideas? > > Hi, > > Check the BIOS for virtualisation or other related options. Some BIOSes > have > the ability to turn those features off, even if the processor normally > supports them > > Regards, > > Gary > -- Best Regards, Aijaz Baig From owner-freebsd-fs@freebsd.org Tue Aug 29 08:58:05 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D0A6DD3627 for ; Tue, 29 Aug 2017 08:58:05 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E512F7D453 for ; Tue, 29 Aug 2017 08:58:03 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A5EC220DD5 for ; Tue, 29 Aug 2017 04:58:02 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 29 Aug 2017 04:58:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=OssHy1scIGzoK5qCocLXJFUIA3zqCcDdD86zHLsTj44=; b=kbWGtpeU OCHPC7DH03bMx+yuayCMi0n3qqbyFOrSVX9AKIG4BNB1NI2L6Ti5pCU3elSeppkG CfYI3J2tl7P+fdrirp2SOPywsLtVpy/QZ9017f/RYUJKonTsF55m4CBWpGrglIBz ETJmW3cMFoUH2bg/LvNwTzC9Ul7wvCDF3las8kFvxYTG3b5ujjpGiz3UGlUaVFBx /048CF6OqOmnZmV/e2XZGCtyTXq9CvZshRDsq9nqWYmKF3EQ0Z6RUFfWbwuRb5E7 E4N9gXmc8fODW0zXc+sorPmMnvYRA3l+HSXdTIrphlKorIN4vxUHOnI4J5tk0H58 gE+qVN5TcHOpOg== X-ME-Sender: X-Sasl-enc: IrR7y/TYrFkXV/fJjNnJW3ycKQHpCD1wREsOBV4M2n10 1503997082 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 5F1962444E for ; Tue, 29 Aug 2017 04:58:02 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 68DD377E for ; Tue, 29 Aug 2017 08:58:01 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id EE88B102A0D; Tue, 29 Aug 2017 10:57:59 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: umount() taking minutes for FUSE filesystems References: <87bmn44ruu.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Tue, 29 Aug 2017 10:57:59 +0200 In-Reply-To: <87bmn44ruu.fsf@vostro.rath.org> (Nikolaus Rath's message of "Thu, 24 Aug 2017 22:45:45 +0200") Message-ID: <87o9qyrbs8.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 08:58:05 -0000 *ping* Anyone able to help? Thanks, -Nikolaus On Aug 24 2017, Nikolaus Rath wrote: > Hello, > > It seems that in some situations, the unmount() system call takes > minutes to unmount fuse filesystems. To reproduce, download a Git > snapshot of libfuse 3 from https://github.com/libfuse/libfuse and do: > > $ md build; cd build > $ meson .. > $ mesonconf -D buildtype=3Ddebug # optional > $ ninja > > Then execute examples/printcap. This will take very long, and all the > time is spent in the unmount(mountpoint, MNT_FORCE) call in > mount_bsd.c:fuse_kern_unmount(). > > Does anyone have an idea what might be causing this and how to fix it? > > My hunch is that it has something to do with libfuse no longer > responding to requests at this point. But I'm at my wits end as to why > and what to do about it.... > > Best, > -Nikolaus > > --=20 > GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > =C2=BBTime flies like an arrow, fruit flies like a Banana.= =C2=AB > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Tue Aug 29 13:13:58 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96062DDAA1F for ; Tue, 29 Aug 2017 13:13:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 84B722033 for ; Tue, 29 Aug 2017 13:13:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TDDwBt070284 for ; Tue, 29 Aug 2017 13:13:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221909] [ZFS] Add a sysctl to toggle send_corrupt_data Date: Tue, 29 Aug 2017 13:13:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 13:13:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221909 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 29 13:28:08 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B9CFDDAFBE for ; Tue, 29 Aug 2017 13:28:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0949D27DD for ; Tue, 29 Aug 2017 13:28:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TDS61f099510 for ; Tue, 29 Aug 2017 13:28:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213915] [zfs] lots of CKSUM errors and sometimes even 'unkown error 122' Date: Tue, 29 Aug 2017 13:28:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 13:28:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213915 Fabian Keil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fk@fabiankeil.de --- Comment #1 from Fabian Keil --- Given the setup described in the forum post is seems conceivable that ZFS temporarily lost access to the disk in which case this could be related to: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218954 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 29 13:41:39 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02E2DDDB4F1 for ; Tue, 29 Aug 2017 13:41:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E53CA341B for ; Tue, 29 Aug 2017 13:41:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TDfcaI032110 for ; Tue, 29 Aug 2017 13:41:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204055] [patch] zfs(8) should not yet list sha512, skein and edonr as supported hash algorithms Date: Tue, 29 Aug 2017 13:41:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 13:41:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204055 Fabian Keil changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #162496|0 |1 is obsolete| | --- Comment #2 from Fabian Keil --- Created attachment 185880 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D185880&action= =3Dedit zfs: Do not advertise edonr which isn't supported yet skein and sha512 weren't supported in 2015 when the original patch was submitted. The updated version only removes the edonr advertisement. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 29 13:42:11 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B097CDDB683 for ; Tue, 29 Aug 2017 13:42:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CA573500 for ; Tue, 29 Aug 2017 13:42:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TDgBEr035153 for ; Tue, 29 Aug 2017 13:42:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204055] [patch] zfs(8) should not yet edonr as supported hash algorithms Date: Tue, 29 Aug 2017 13:42:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 13:42:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204055 Fabian Keil changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[patch] zfs(8) should not |[patch] zfs(8) should not |yet list sha512, skein and |yet edonr as supported hash |edonr as supported hash |algorithms |algorithms | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 29 13:43:22 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77634DDB7B0 for ; Tue, 29 Aug 2017 13:43:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6589A361C for ; Tue, 29 Aug 2017 13:43:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TDhMIF040119 for ; Tue, 29 Aug 2017 13:43:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204055] [patch] zfs(8) should not yet list edonr as supported hash algorithm Date: Tue, 29 Aug 2017 13:43:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 13:43:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204055 Fabian Keil changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[patch] zfs(8) should not |[patch] zfs(8) should not |yet edonr as supported hash |yet list edonr as supported |algorithms |hash algorithm --- Comment #3 from Fabian Keil --- Spelling is hard, title corrected. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 29 14:08:07 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2DC4DDBF93 for ; Tue, 29 Aug 2017 14:08:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C13A5632F3 for ; Tue, 29 Aug 2017 14:08:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TE87fO016051 for ; Tue, 29 Aug 2017 14:08:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 178388] [zfs] [patch] allow up to 8MB recordsize Date: Tue, 29 Aug 2017 14:08:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 14:08:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D178388 Fabian Keil changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fk@fabiankeil.de --- Comment #6 from Fabian Keil --- Looks like this can be closed. On pools with feature@large_blocks enabled, OpenZFS supports block sizes up to 16MB "now" (if one sets vfs.zfs.max_recordsize accordingly and ignores the Dragon warning in the sysctl description). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 29 15:02:35 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE657DDDC0B for ; Tue, 29 Aug 2017 15:02:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f67.google.com (mail-oi0-f67.google.com [209.85.218.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B59A065B9D for ; Tue, 29 Aug 2017 15:02:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f67.google.com with SMTP id k77so3230906oib.2 for ; Tue, 29 Aug 2017 08:02:35 -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:reply-to:in-reply-to:references :from:date:message-id:subject:to:content-transfer-encoding; bh=0IhF2Ww2P4gbAOPMmSuegEhw59m7HQOKSakMl7qryOo=; b=McYybq64z3lopcdD8WA4XQ9F/aIjn40HKm0mqNCkWxsCpg2R1oHzagvVWVW+EpO1LX 9gOKAjUwiBGyTYrU1Ipw/og8amwH3hAOEENciCmAnoQ2npM946V9LrgQNtNqYaVqBkye 30Z3u2XYEiqvoobnN0Wy2yj/B4WF21jU5SjgOAV6ZAkPKTfOtWSUo6XwYmcDixScO6AJ w45rP78dZW+NRSKMZnTe483+IJMP8O4SbJJ+0k3+TngvKuCnVRcrjJb4yif9U13CklN8 B/o4UI5E9Ro6eBMTOGEddhTk4n/aGd6/0GfNsjlSsIz9KDgTLTkiOPOSTJzi6DYlRu4R r/Gg== X-Gm-Message-State: AHYfb5hlB7nQ1hdSdEpMHTZ4h5fRnVbTNf3VIbK5VbtAXRcQAqqIpTYn pTB/X+KjZjDejJjJ5IE= X-Received: by 10.202.232.84 with SMTP id f81mr629583oih.121.1504018952443; Tue, 29 Aug 2017 08:02:32 -0700 (PDT) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com. [209.85.223.178]) by smtp.gmail.com with ESMTPSA id g12sm3118623oib.6.2017.08.29.08.02.32 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Aug 2017 08:02:32 -0700 (PDT) Received: by mail-io0-f178.google.com with SMTP id g33so17126686ioj.3 for ; Tue, 29 Aug 2017 08:02:32 -0700 (PDT) X-Received: by 10.36.14.216 with SMTP id 207mr2454021ite.151.1504018951870; Tue, 29 Aug 2017 08:02:31 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.81.131 with HTTP; Tue, 29 Aug 2017 08:02:31 -0700 (PDT) In-Reply-To: <87o9qyrbs8.fsf@vostro.rath.org> References: <87bmn44ruu.fsf@vostro.rath.org> <87o9qyrbs8.fsf@vostro.rath.org> From: Conrad Meyer Date: Tue, 29 Aug 2017 08:02:31 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: umount() taking minutes for FUSE filesystems To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 15:02:36 -0000 Hey Nikolaus, A first cut debug tactic might be running 'procstat -kk ' to see where it is spending time in the kernel. I haven't had time to try and reproduce this myself, sorry. Best, Conrad On Tue, Aug 29, 2017 at 1:57 AM, Nikolaus Rath wrote: > *ping* > > Anyone able to help? > > Thanks, > -Nikolaus > > On Aug 24 2017, Nikolaus Rath wrote: >> Hello, >> >> It seems that in some situations, the unmount() system call takes >> minutes to unmount fuse filesystems. To reproduce, download a Git >> snapshot of libfuse 3 from https://github.com/libfuse/libfuse and do: >> >> $ md build; cd build >> $ meson .. >> $ mesonconf -D buildtype=3Ddebug # optional >> $ ninja >> >> Then execute examples/printcap. This will take very long, and all the >> time is spent in the unmount(mountpoint, MNT_FORCE) call in >> mount_bsd.c:fuse_kern_unmount(). >> >> Does anyone have an idea what might be causing this and how to fix it? >> >> My hunch is that it has something to do with libfuse no longer >> responding to requests at this point. But I'm at my wits end as to why >> and what to do about it.... >> >> Best, >> -Nikolaus >> >> -- >> GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F >> >> =C2=BBTime flies like an arrow, fruit flies like a Banana.= =C2=AB >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > -- > GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > =C2=BBTime flies like an arrow, fruit flies like a Banana.= =C2=AB > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Tue Aug 29 22:25:24 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9A91DE736E for ; Tue, 29 Aug 2017 22:25:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C81A47371A for ; Tue, 29 Aug 2017 22:25:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TMPOH1029280 for ; Tue, 29 Aug 2017 22:25:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204055] [patch] zfs(8) should not yet list edonr as supported hash algorithm Date: Tue, 29 Aug 2017 22:25:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 22:25:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204055 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: emaste Date: Tue Aug 29 22:24:22 UTC 2017 New revision: 323002 URL: https://svnweb.freebsd.org/changeset/base/323002 Log: zfs: do not advertise edonr which is not yet supported illumos 4185 ("add new cryptographic checksums to ZFS: SHA-512, Skein, Edon-R") was intentionally merged only partially in r289422, without adding support for skein, sha512 and edonr on FreeBSD. Support for skein and sha512 was added later on, but edonr is still not implemented in FreeBSD. Prior to this commit zfs(8) correctly rejected edonr, but with an error message that claimed support: fk@r500 ~ $zfs set checksum=3Dedonr tank cannot set property for 'tank': 'checksum' must be one of 'on | off | fletcher2 | fletcher4 | sha256 | sha512 | skein | edonr' PR: 204055 Submitted by: Fabian Keil Approved by: allanjude Obtained from: ElectroBSD MFC after: 1 week Changes: head/sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 29 22:25:58 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43D26DE73D8 for ; Tue, 29 Aug 2017 22:25:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 325A3737AA for ; Tue, 29 Aug 2017 22:25:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7TMPvi9030066 for ; Tue, 29 Aug 2017 22:25:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204055] [patch] zfs(8) should not yet list edonr as supported hash algorithm Date: Tue, 29 Aug 2017 22:25:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: emaste@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 22:25:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204055 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress Assignee|freebsd-fs@FreeBSD.org |emaste@freebsd.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 30 01:48:35 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46A0FDEBA46 for ; Wed, 30 Aug 2017 01:48:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 304427E1DD for ; Wed, 30 Aug 2017 01:48:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7U1mY17000820 for ; Wed, 30 Aug 2017 01:48:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 218626] [PATCH] cuse: new error code CUSE_ERR_NO_DEVICE (ENODEV) Date: Wed, 30 Aug 2017 01:48:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 01:48:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218626 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 30 02:54:23 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FB0ADECCB4 for ; Wed, 30 Aug 2017 02:54:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DE1F7FDAF for ; Wed, 30 Aug 2017 02:54:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7U2sNdg008553 for ; Wed, 30 Aug 2017 02:54:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221909] [ZFS] Add a sysctl to toggle send_corrupt_data Date: Wed, 30 Aug 2017 02:54:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 02:54:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221909 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaste@freebsd.org --- Comment #1 from Ed Maste --- Would you care to submit this as a pull request at https://github.com/openzfs/openzfs so it can be discussed/debated there? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 30 07:23:49 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0ACBBDF18AF for ; Wed, 30 Aug 2017 07:23:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ED5461EE2 for ; Wed, 30 Aug 2017 07:23:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7U7NmBu040821 for ; Wed, 30 Aug 2017 07:23:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 218626] [PATCH] cuse: new error code CUSE_ERR_NO_DEVICE (ENODEV) Date: Wed, 30 Aug 2017 07:23:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 07:23:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218626 --- Comment #1 from Hans Petter Selasky --- Hi, Please also describe the new error code in: lib/libcuse/cuse.3 Patch looks good! --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Aug 30 07:25:53 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94A5DDF199D for ; Wed, 30 Aug 2017 07:25:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 829AF1FC7 for ; Wed, 30 Aug 2017 07:25:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7U7PrLs043747 for ; Wed, 30 Aug 2017 07:25:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 218626] [PATCH] cuse: new error code CUSE_ERR_NO_DEVICE (ENODEV) Date: Wed, 30 Aug 2017 07:25:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 07:25:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218626 --- Comment #2 from Hans Petter Selasky --- And also please bump the CUSE_VERSION macro. --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Aug 31 10:38:42 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BBDF7E1B6A4 for ; Thu, 31 Aug 2017 10:38:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA48572623 for ; Thu, 31 Aug 2017 10:38:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7VAcgak084940 for ; Thu, 31 Aug 2017 10:38:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221909] [ZFS] Add a sysctl to toggle send_corrupt_data Date: Thu, 31 Aug 2017 10:38:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: fk@fabiankeil.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 10:38:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221909 --- Comment #2 from Fabian Keil --- The patch isn't relevant for OpenZFS upstream. On illumos-based platforms the send_corrupt_data variable is conveniently set with mdb. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Aug 31 19:45:41 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAB99E04AA7 for ; Thu, 31 Aug 2017 19:45:41 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (unknown [IPv6:2001:470:1f0f:3ad:bb:dcff:fe50:d900]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 89D8165023 for ; Thu, 31 Aug 2017 19:45:40 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To: References:Message-ID:CC:To:From:Subject:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=4K0PjTZaqOhPohm3oMHwl+DR4VqZzqAb8oWesQVS8ho=; b=VpPsZmxp8aYtdy2T3HxdaA5VFa 1aBx1c/50sQJe+qJyDEoHdu4chYPjZ3iaGGlXDfwZfn8yYMmTfM4qbhvM5R9eBuJcqr6usuQU5r6l 668NVHOzIliZ28aIACq4qQiOve+mdUAPOhqtT9nnNcXeNpkOhmUZRDCedsJRUry3YB2g=; Received: from [74.203.163.58] (port=17091 helo=[10.106.10.43]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dnVPH-0003Rm-KL; Thu, 31 Aug 2017 14:45:39 -0500 User-Agent: Microsoft-MacOutlook/f.26.0.170822 Date: Thu, 31 Aug 2017 14:45:09 -0500 Subject: Re: ENAMETOOLONG? From: Larry Rosenman To: Martin Simmons CC: Message-ID: Thread-Topic: ENAMETOOLONG? References: <20170822141419.v6ely424bjvcnzoj@lrosenman.local> <201708231238.v7NCc4f7008608@higson.cam.lispworks.com> <14F658A8-23DB-49DF-9AA3-5BD45BA26BEA@lerctr.org> In-Reply-To: <14F658A8-23DB-49DF-9AA3-5BD45BA26BEA@lerctr.org> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 19:45:41 -0000 On 8/23/17, 9:15 AM, "Larry Rosenman" wrote: On 8/23/17, 7:38 AM, "Martin Simmons" wrote: >>>>> On Tue, 22 Aug 2017 09:14:19 -0500, Larry Rosenman said: > > Are there plans to increase the max length for zfs? > > [1239928] ZFS WARNING: Unable to create ZVOL zroot/vm-bhyve/freebsd11/disk0@zfs-auto-snap_hourly-2017-08-22-09h00 (error=63). I think this is hitting the limit on SPECNAMELEN when it tries to create the device node. __Martin Any chance of that limit be increased? Any takers? sys/sys/param.h:#define SPECNAMELEN 63 /* max length of devicename */ From owner-freebsd-fs@freebsd.org Thu Aug 31 20:51:16 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC98CE05C5A for ; Thu, 31 Aug 2017 20:51:16 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D34E6712C for ; Thu, 31 Aug 2017 20:51:16 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-io0-x232.google.com with SMTP id k22so5824896iod.2 for ; Thu, 31 Aug 2017 13:51:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Zk+VUgLINEwUOnFekcyi2Gdl8FbxulqHMTJZf92NheE=; b=mAvItDesz902+ohiyw+z8epGHpLPMbRlvs5wSLCe4o5IaAM3YzUhV2U5MXbiSpmD7H CIySrKFdr4t/bze9cgepnS6yT3XJvMk4qBceyR8fxikw8wxayPqX/vO2GolFCqTgoHAc EbJipkhLfmBIHrKDIzN5zDR/vWpqcLmqJkB+kDdMcbzB2thwJtLioEmvsICpthiqkgW+ Hzovqh55RMq2Ciu54rSBTA3pjeup2HHcEowsB2AZITJG0+T5obyHtIGCmjySEjUtFwlK wHFqrq4GKQgTkk67GjhtjIBEFwNGqrgW6mAv/S8R5i4J37Co01DhRVEPE02ZmHpDegCL L4yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Zk+VUgLINEwUOnFekcyi2Gdl8FbxulqHMTJZf92NheE=; b=mx2CYZnZSM0um83HBqUZkrs6mcuHG/0twWedl25RrwsZ19P0vtnxYCGO/qWKKNyMjZ csgbufzXsdVfWorTt2gCUk+mCKeUfuiJ3U2HxC1Ze4tdH00MgQJm6c/vrZs2P5vS8fr4 zHQ/8phM19Zy8yGirQ7WCXOCA2EGlG9vXse28GvI6QgK4knhS7CWUpHhpBh/dh9p+V8J 4CyAed7el+QPqg1pvJuctENuWOAIfZO5L2UFAwT4RwzFABKS6cWGEI4GuArvJ0Qpc34d dJpajL9u1X0UQI8YrFA6KZ+olo7er8ZZ//ivubQLXr6LkBmod6dGo6poQY5xDPN87SK4 2/TQ== X-Gm-Message-State: AHYfb5iEKY7Yd/LrshVKOQmAoyvUghbHdRCe3NMqjkWzLkNdv3DChexF YQjEWxxCOBUZ2Eii0gu2Pd4WJNs2b+R+ X-Google-Smtp-Source: ADKCNb7Tde+hIiYSJ6G5io1fpzBDwHxzXXI0p4QxD8sLrE+zcr+WfkVkGm4TDYSH0ScaDkffS27hHjyslAiLofNb114= X-Received: by 10.36.172.31 with SMTP id s31mr2455572ite.74.1504212675823; Thu, 31 Aug 2017 13:51:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.15.80 with HTTP; Thu, 31 Aug 2017 13:51:14 -0700 (PDT) In-Reply-To: References: <20170822141419.v6ely424bjvcnzoj@lrosenman.local> <201708231238.v7NCc4f7008608@higson.cam.lispworks.com> <14F658A8-23DB-49DF-9AA3-5BD45BA26BEA@lerctr.org> From: Xin LI Date: Thu, 31 Aug 2017 13:51:14 -0700 Message-ID: Subject: Re: ENAMETOOLONG? To: Larry Rosenman Cc: Martin Simmons , freebsd-fs Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 20:51:17 -0000 This have broad impact and would a) increase kernel stack usage for many routines and b) break some backward compatibility ABIs so if someone does it please make sure that the change gets carefully reviewed/audited. Cheers, On Thu, Aug 31, 2017 at 12:45 PM, Larry Rosenman wrote: > On 8/23/17, 9:15 AM, "Larry Rosenman" wrote: > > > > > On 8/23/17, 7:38 AM, "Martin Simmons" wrote: > > >>>>> On Tue, 22 Aug 2017 09:14:19 -0500, Larry Rosenman said: > > > > Are there plans to increase the max length for zfs? > > > > [1239928] ZFS WARNING: Unable to create ZVOL zroot/vm-bhyve/freebsd11/disk0@zfs-auto-snap_hourly-2017-08-22-09h00 (error=63). > > I think this is hitting the limit on SPECNAMELEN when it tries to create the > device node. > > __Martin > > > Any chance of that limit be increased? > > > Any takers? > > sys/sys/param.h:#define SPECNAMELEN 63 /* max length of devicename */ > > > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Fri Sep 1 15:15:28 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBEF6E13FCB for ; Fri, 1 Sep 2017 15:15:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DA46C75BD1 for ; Fri, 1 Sep 2017 15:15:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v81FFR0A096662 for ; Fri, 1 Sep 2017 15:15:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 184013] [fusefs] truecrypt broken (probably fusefs issue) Date: Fri, 01 Sep 2017 15:15:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kb3ngb@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2017 15:15:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D184013 --- Comment #5 from jonathan derose --- i know it has been a while since i posted anything here, but give up was the last thing i did.. since then i've actually forked the code, and also moved, i have a working portfile for 11 i will put back here when i get my workstation power conne= cted later this week. the problem was with UFS; i forget what the exact thing was, as i looked at that long ago, but it wasn't going to be resolved easily and so i chose to focus on finding a common format that would work reasonably across macos, l= inux and FreeBSD. although my effort primarily targets working on FreeBSD, i also have maintained support for the other two. In the process, I completely rew= rote the file system detection/arbitration code used for FreeBSD to use a little magic now. th it's not simply the dumb version they had included; we try a little harder now...in fact the freebsd code for this task was little more = than a stub to be finished later...anyhow my solution was to change the default filesystem to the ext3fs provided by the kernel which works wonderfully, and i've also patched OSXfuse to work with it, and made it the default there, a= nd in the linux version. alper akcan was kind enough to accept my changes to osxfuse and pull them back in to his distribution. i've looked in to adding support for ZFS and i think it is very possible although it will take me so= me time and i'm rather swamped right now, i have a plan of attack, and i plan = on attacking it. for now i have a version up on github, at http://github.com/adouble42/nemesis-current and a more current working copy= on my internal gitweb accessible via tor at http://qpbt3kpraplo7ias.onion/?p=3Dnemesis.git;a=3Dsummary the onion link is probably more current by far than github, it also might require some monkeying around as it's what my current effort is. i've had to change the name of the project and strengthened some things such as the KDF, although i can easily change it to read existing containers with the old KDF iterations for the fellow from several years back, should he still have this issue. linux would have been using ext3 anyway so that would work just fine. the portfile pulls a known stable revision from my git and i plan on submit= ting it for review shortly. it is my intention to continue to maintain the fork,= at the time i answered this, had no idea i'd be going that far...should anyone see this that is or knows the right person to talk to regarding contributin= g a port please do reach out thanks tl;dr UFS is hopelessly broken or pointlessly at least as it is here; it's = an easier effort to rewrite core_freebsd to use zfs and ext3. my forks changes= in that respect should backport to the original as drop in; will attempt altho= ugh i do suggest giving the fork a chance. it was a lot of work to get this ba= ck on track and honestly moving forward seems the best idea given the amount of effort involved it seems slightly crazy not to improve the rest in order to= at least mitigate the effects of Moore's law. that's not to say compatibility = with existing data be damned , of course... http://github.com/adouble42/nemesis-current or http://qpbt3kpraplo7ias.onion/?p=3Dnemesis.git;a=3Dsummary onion more current portfile to follow --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Sep 2 12:40:25 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E27FDE11505 for ; Sat, 2 Sep 2017 12:40:25 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A75231870; Sat, 2 Sep 2017 12:40:25 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id c13so4882098itb.0; Sat, 02 Sep 2017 05:40:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FtePJdYfCuJJbr7WdYt6lQjkfFxQ/NLeB7+00YOvuoc=; b=pvYXMEYeAUI45X4kPvH8QudXLUOi9LoDOfo8/evNmz67vyXXhoexMvRND6xk0+OKr/ 5hb31ktCp9qBsZK21PZrKnOgk/vbPJK4UCRGRNTt/3FFwuHAPSjwYgtlLpYOUJCGOgwh +p/sokodJK3HuRBOE1q3We8FOfuEMWDI6JnPTFZErz32Cw9/mNFamCVXjLrOCi0XShsD pXjv95GDgWC0idznWY+I9T1upqdq3alPaF82l6rnouCRoBrfoJ7D8Gbf+Bjzsy5+35x/ uA3c0hWBGted0+UuqSwVQr+vhR4QEELMETRNixUFnKI+YW41Mt8TR9D42/S8/qR9PDFp YsvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FtePJdYfCuJJbr7WdYt6lQjkfFxQ/NLeB7+00YOvuoc=; b=UpdAsSOswHxrNvhXBhy2umvFL9S3XedvvICyTUb4LMBI/CQkkck+AUtMSQKFK5X17E RVpOK+Kgp0982TCA6OKL2CZ1v1wITtl3Tnp7toAGEIcjYpE30tEBUbMOic4gSYXg+brK PvzP09qlKAAxnpknn//FlMsDpxLw/AYSy+KBVk9g8jRRDHw/UHN95tVTa6mhCHA+hN7u n0kDIfwaavoTB+TsvCJyvMSPmiyAG3R0FUzntQZQ+EN1cJG7Wfr5y9XHDetpfn5JSl/p WnmpdtUhJKi+87GkYx4PJpyoyDYWepJX3hnbYuD2iS3iBjuwAdy+fKKQ2EXYuYElvIx7 fkEg== X-Gm-Message-State: AHPjjUi4kwlvLn7pYcyXjFBGuvKgP12bX0qKcB928+8HF7O+eA+YHSHf PtneRGgT18C8MjhESoKZBhbAnUJpPQ== X-Google-Smtp-Source: ADKCNb4dIJ3seu5QXgFp2vo2g8RyfmOwzEw9E+UFo9rLVGiNqblV5Qx/DRPdBtk8ytBtOZmWRoWfv0ABB3DazA2K4tI= X-Received: by 10.36.29.193 with SMTP id 184mr1272801itj.97.1504356024543; Sat, 02 Sep 2017 05:40:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.22.66 with HTTP; Sat, 2 Sep 2017 05:40:23 -0700 (PDT) In-Reply-To: References: <201708250251.v7P2pwcl029687@chez.mckusick.com> <20170827195428.49400124AE9F@mail.bitblocks.com> <20170828132647.GA60563@in-addr.com> From: Aijaz Baig Date: Sat, 2 Sep 2017 18:10:23 +0530 Message-ID: Subject: Re: Tips on remote debugging for filesystem code To: Gary Palmer Cc: Bakul Shah , Kirk McKusick , Julian Elischer , freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2017 12:40:26 -0000 I was finally able to deploy a FreeBSD-Current VM on Bhyve but even with that setup I face a similar issue For instance I put a breakpoint on 'ffs_read' and let the debugged VM continue but the control is neither returned to (k)gdb nor does the VM actually run. It appears hung. Is there something within the ffs/ufs code that I need to be aware of that it doesn't facilitate this sort of debugging? Or is it because Bhyve is being run on FreeBSD which is itself run on another hypervisor? Will that affect this? On Mon, Aug 28, 2017 at 7:03 PM, Aijaz Baig wrote: > HI Gary > > Just checked that. Indeed that was the case. In addition I was running > FreeBSD on top of vmware hypervisor and had not allowed hardware > acceleration features pass through to the FreeBSD VM. It is now working! > Need to explore more on getting it to connect to GDB > > Perhaps you'll see a thread soon for it (Has anything worked perfectly for > the first time ever?? ;) )! > > On Mon, Aug 28, 2017 at 6:56 PM, Gary Palmer wrote: > >> On Mon, Aug 28, 2017 at 01:12:09PM +0530, Aijaz Baig wrote: >> > Thanks a lot bakul. Will certain look into this >> > >> > Nevertheless I got hold of a PowerEdge 320 system which DOES have a >> POPCNT >> > instruction which shows support for V-x support via EPT but I still get >> the >> > same error there >> > >> > sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 2048M -t tap0 -d >> guest.img -i >> > -I FreeBSD-10.3-RELEASE-amd64-bootonly.iso fbsd10 >> > Launching virtual machine "fbsd10" ... >> > vm_create: Device not configured >> > >> > dmesg: >> > vmx_init: processor does not support VMX operation >> > >> > cat /var/run/dmesg.boot | grep -i popcnt >> > >> > Features2=0xffba2203> SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> >> > >> > Features2=0xffba2203> SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> >> > >> > Any ideas? >> >> Hi, >> >> Check the BIOS for virtualisation or other related options. Some BIOSes >> have >> the ability to turn those features off, even if the processor normally >> supports them >> >> Regards, >> >> Gary >> > > > > -- > > Best Regards, > Aijaz Baig > -- Best Regards, Aijaz Baig From owner-freebsd-fs@freebsd.org Sat Sep 2 16:40:17 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECDEAE1B5B7 for ; Sat, 2 Sep 2017 16:40:17 +0000 (UTC) (envelope-from bsd@vink.pl) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A976B685BD for ; Sat, 2 Sep 2017 16:40:17 +0000 (UTC) (envelope-from bsd@vink.pl) Received: by mail-qk0-x22b.google.com with SMTP id p67so10728082qkd.2 for ; Sat, 02 Sep 2017 09:40:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vink-pl.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=UUggcenKkHFtyjts4hR1K8R9ZjHsvZSHsDtSrHMcd2g=; b=DsNyj0BLJGEBRdmSx7h8SPNj47GhfUhw3MCOJQ7o3pGDu8oZaGwUo4a9G6Pv2kgv1c MMKkLyRygBieHEk3fZbu1580DGI5424pza2hHXv6NIm4BbLE3H7ALCfvW1dhkQI11odZ m9LTkzH2NYYaGi5pIY0fGfI8lwgj9mgKLI3RNioemhKMp/ZyJ+fYwwtF+DQbSDBiLPGe 5t+GpvBsSh5h3QrBkXBhyr1/46H5C9cPzQtBj/88sdgAyFdpR7boQ/IAkLJUKF1CdQql 5HZz+c6SUL4knDUXL9NyaNy176NPzoSUG16tSV9xm8b/GqS7rc1tgU2bjmkJ+5nz23+c 9GFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UUggcenKkHFtyjts4hR1K8R9ZjHsvZSHsDtSrHMcd2g=; b=AqRUJJ7raCtad5YFUjhE45JnfoH/5cSscNXs6T9QWRcY4MfhO2n6sNqYbjxpu5MniU uZsQNFza2IFVJHtflNvA7nWVRFUhtztxRU6DP3PThxNkDX1R4z/VDImmn/Cx2swtPTY8 ia93KV4h8xYM/PxoK0shxkWKachC2azFCz+JeidNd3XQxYoGsBil20muXvxiiLHkj9St 3jANbccwikQYgkhRXMeSwlS7+xQy4gxLLDI8hEMhlmsvz0TPUk/efZ3LyR8eG60eHHxi 1OvZcIfCQKMITya8GQaQ9j1/T0vpSSkfFySTr0q50DtIUYHXSrfTyB4/WJubE9xd2ce0 95cw== X-Gm-Message-State: AHPjjUg+yTW+QitEQYFT96XNqBGD5cVV/P4ouau9ERHXHcIdQDUUJsxH sOqSPmDeGwFzM0L08B0= X-Received: by 10.55.118.132 with SMTP id r126mr7570777qkc.169.1504370416305; Sat, 02 Sep 2017 09:40:16 -0700 (PDT) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com. [209.85.220.177]) by smtp.gmail.com with ESMTPSA id s127sm1030899qkh.63.2017.09.02.09.40.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Sep 2017 09:40:16 -0700 (PDT) Received: by mail-qk0-f177.google.com with SMTP id l65so10780225qkc.0 for ; Sat, 02 Sep 2017 09:40:16 -0700 (PDT) X-Google-Smtp-Source: ADKCNb4qR/owGMoahU2CILwnUxNg5xGQWS3qgP8Hx5aX0OIK4YBhrvMDpacjrZiE1g20+21NG/gSC+oR+BdHD5Y7iDk= X-Received: by 10.55.75.216 with SMTP id y207mr7952016qka.140.1504370415649; Sat, 02 Sep 2017 09:40:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.156.197 with HTTP; Sat, 2 Sep 2017 09:40:15 -0700 (PDT) From: Wiktor Niesiobedzki Date: Sat, 2 Sep 2017 18:40:15 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Resolving errors with ZVOL-s To: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2017 16:40:18 -0000 Hi, I have recently encountered errors on my ZFS Pool on my 11.1-R: $ uname -a FreeBSD kadlubek 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 11:55:48 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # zpool status -v tank pool: tank state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: scrub repaired 0 in 5h27m with 0 errors on Sat Sep 2 15:30:59 2017 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 98 mirror-0 ONLINE 0 0 196 gpt/tank1.eli ONLINE 0 0 196 gpt/tank2.eli ONLINE 0 0 196 errors: Permanent errors have been detected in the following files: dkr-test:<0x1> dkr-test is ZVOL that I use within bhyve and indeed - within bhyve I have noticed I/O errors on this volume. This ZVOL did not have any snapshots. Following the advice mentioned in action I tried to restore the ZVOL: # zfs desroy tank/dkr-test But still errors are mentioned in zpool status: errors: Permanent errors have been detected in the following files: <0x5095>:<0x1> I can't find any reference to this dataset in zdb: # zdb -d tank | grep 5095 # zdb -d tank | grep 20629 I tried also getting statistics about metadata in this pool: # zdb -b tank Traversing all blocks to verify nothing leaked ... loading space map for vdev 0 of 1, metaslab 159 of 174 ... 94.5G completed (1059MB/s) estimated time remaining: 0hr 25min 47sec And now to my questions: 1. Do I interpret correctly, that this situation is probably due to error during write, and both copies of the block got checksum mismatching their data? 2. Is there any way to From owner-freebsd-fs@freebsd.org Sat Sep 2 17:17:19 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8225FE1D07C for ; Sat, 2 Sep 2017 17:17:19 +0000 (UTC) (envelope-from bsd@vink.pl) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E0B46A160 for ; Sat, 2 Sep 2017 17:17:19 +0000 (UTC) (envelope-from bsd@vink.pl) Received: by mail-qk0-x231.google.com with SMTP id a77so10865886qkb.1 for ; Sat, 02 Sep 2017 10:17:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vink-pl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=vv4qsm6Ksdphx/Mmf/s0YoE5/kgaTFZbWwcLMktEk1I=; b=r1mIVyc7HBzyz0TObQ5Z37ZgQpuso2PfmGPJK0uYqY8PftgWjYHCKigfp05zmRDK9K xkzaTDQg5enypPDmi2VuJUmtuoj/z4P/n83pBfw92uiYikdt+BhmEoyOH08TAmIA7Eo1 Z8OVtE3tcLtsxEv73jTfZnsI9zOjcgRar6Khj4ZmxK9ekuWlgqCA7we3is3M10SnYl4+ RquUAI3u/T64rO1s0aRwnG/cZKTqqk7jB+CKMMUZKWDEeAJLH91db7rmIzEaQjhtUQ81 q8zj7Izxkeq7G9NZXiSaxqM4WmnpDlqOugd98PCGi/IAICAQDNutL/0h/n1iZog3eLF7 91tQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=vv4qsm6Ksdphx/Mmf/s0YoE5/kgaTFZbWwcLMktEk1I=; b=VwnX6NqiZqSfHfjhLiZe/UH4OLfH2RgBxCq9uHfczf8dlYSSR2p1r08WV12jEGFh9P /XR5EKWsFTT+aR3a+1o28HxvmiRr5z4nXJXzsc0cdROIMeBVN0jb3XdR4qY+TKQBz0Jh QqK24i7j29xxBVeSzgQSAHoAq4tun5nYZAQVVUi14Rz4NOJGKhXS1aKyPRsp0/W4Jcwk J/3r49RYqk86ICGW2xR3A5P9B6/0EcOVveKsFISQqUfszjQhf1Jz7sanU4Ls31H3gkmw jT6l4cAH4/W/t4g2xTrgCPFiWAaeXF6kPPwBy1+oZ+SwshPHF80FSqITYtS7FdESPlhD S8Mw== X-Gm-Message-State: AHPjjUjRTTLIGrwQKFA852NvnlJ7fXeAwBMJ5PnAaFNcZx6iujn1Eq9J HAXAAJZHdr9DvD/KXUU= X-Received: by 10.55.103.151 with SMTP id b145mr7336659qkc.78.1504372637948; Sat, 02 Sep 2017 10:17:17 -0700 (PDT) Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com. [209.85.220.179]) by smtp.gmail.com with ESMTPSA id s124sm1097862qkc.5.2017.09.02.10.17.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Sep 2017 10:17:17 -0700 (PDT) Received: by mail-qk0-f179.google.com with SMTP id k126so10852912qkb.4 for ; Sat, 02 Sep 2017 10:17:17 -0700 (PDT) X-Google-Smtp-Source: ADKCNb6GmqCGzTeMVt1WfMwdrfmhegV21jekzf3hev3MqpJi+ILoFCUvEGwOLPcMVnUwykNmqbNpOjRZWp0r/xG1sis= X-Received: by 10.233.237.12 with SMTP id c12mr8238177qkg.268.1504372636993; Sat, 02 Sep 2017 10:17:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.156.197 with HTTP; Sat, 2 Sep 2017 10:17:16 -0700 (PDT) In-Reply-To: References: From: Wiktor Niesiobedzki Date: Sat, 2 Sep 2017 19:17:16 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Resolving errors with ZVOL-s To: freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2017 17:17:19 -0000 Hi, I have recently encountered errors on my ZFS Pool on my 11.1-R: $ uname -a FreeBSD kadlubek 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 11:55:48 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # zpool status -v tank pool: tank state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: scrub repaired 0 in 5h27m with 0 errors on Sat Sep 2 15:30:59 2017 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 98 mirror-0 ONLINE 0 0 196 gpt/tank1.eli ONLINE 0 0 196 gpt/tank2.eli ONLINE 0 0 196 errors: Permanent errors have been detected in the following files: dkr-test:<0x1> dkr-test is ZVOL that I use within bhyve and indeed - within bhyve I have noticed I/O errors on this volume. This ZVOL did not have any snapshots. Following the advice mentioned in action I tried to restore the ZVOL: # zfs desroy tank/dkr-test But still errors are mentioned in zpool status: errors: Permanent errors have been detected in the following files: <0x5095>:<0x1> I can't find any reference to this dataset in zdb: # zdb -d tank | grep 5095 # zdb -d tank | grep 20629 I tried also getting statistics about metadata in this pool: # zdb -b tank Traversing all blocks to verify nothing leaked ... loading space map for vdev 0 of 1, metaslab 159 of 174 ... No leaks (block sum matches space maps exactly) bp count: 24426601 ganged count: 0 bp logical: 1983127334912 avg: 81187 bp physical: 1817897247232 avg: 74422 compression: 1.09 bp allocated: 1820446928896 avg: 74527 compression: 1.09 bp deduped: 0 ref>1: 0 deduplication: 1.00 SPA allocated: 1820446928896 used: 60.90% additional, non-pointer bps of type 0: 57981 Dittoed blocks on same vdev: 296490 And zdb got stuck using 100% CPU And now to my questions: 1. Do I interpret correctly, that this situation is probably due to error during write, and both copies of the block got checksum mismatching their data? And if it is a hardware problem, it is probably something other than disk? (No, I don't use ECC RAM) 2. Is there any way to remove offending dataset and clean the pool of the errors? 3. Is my metadata OK? Or should I restore entire pool from backup? 4. I tried also running zdb -bc tank, but this resulted in kernel panic. I might try to get the stack trace once I get physical access to machine next week. Also - checksum verification slows down process from 1000MB/s to less than 1MB/s. Is this expected? 5. When I work with zdb (as as above) should I try to limit writes to the pool (e.g. by unmounting the datasets)? Cheers, Wiktor Niesiobedzki PS. Sorry for previous partial message.