From owner-freebsd-fs@freebsd.org Mon May 29 10:23:30 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 82D7DCFAEA1 for ; Mon, 29 May 2017 10:23:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A3701740DA; Mon, 29 May 2017 10:23:29 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA14688; Mon, 29 May 2017 13:23:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dFHpZ-000MNg-Cy; Mon, 29 May 2017 13:23:21 +0300 Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. To: lev@FreeBSD.org, freebsd-fs@FreeBSD.org References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> <1279842496.20170529132006@serebryakov.spb.ru> From: Andriy Gapon Message-ID: <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> Date: Mon, 29 May 2017 13:22:25 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <1279842496.20170529132006@serebryakov.spb.ru> Content-Type: text/plain; charset=windows-1250 Content-Language: en-US Content-Transfer-Encoding: 8bit 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, 29 May 2017 10:23:30 -0000 On 29/05/2017 13:20, Lev Serebryakov wrote: > Hello Andriy, > > Monday, May 29, 2017, 9:09:58 AM, you wrote: > >>> (2) When I've reverted to r318576, this patch helps! >> You probably meant r318716 again here? > Nope. r318576. Sorry, it was my confusion, I read "reverted to r318576" as "reverted r318576". > I've found "snapshot .." bug at r318576 (see my first message), > so when "latest" (I'm using local mirror, so it could be > not-really-latest-one) revision — r319076 — crashed, I've reverted to > exactly this "proven" revision — r318576. Patch for "snapshot .." was tested > at r318576, and crash with and without patch for "snapshot" was at r319076. > >> If yes, then it's probably exactly the same issue as we had in head: r308826. >> Could you please test if that change helps? >> I'll take care of this. > Now, as r319091 was committed, I'm building new fresh kernel. Thank you. Please let me know how it goes. -- Andriy Gapon