From owner-freebsd-fs@freebsd.org Mon May 29 12:46:31 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 B667ACFE38D for ; Mon, 29 May 2017 12:46:31 +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 D050377FF9; Mon, 29 May 2017 12:46:30 +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 PAA15009; Mon, 29 May 2017 15:46:28 +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 1dFK44-000MUW-Mh; Mon, 29 May 2017 15:46:28 +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> <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> From: Andriy Gapon Message-ID: Date: Mon, 29 May 2017 15:45:33 +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: <5d9dbe2e-9d51-0df2-1280-25ccbe710900@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US 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: Mon, 29 May 2017 12:46:31 -0000 On 29/05/2017 15:43, Lev Serebryakov wrote: > On 29.05.2017 13:22, Andriy Gapon wrote: > >>> Now, as r319091 was committed, I'm building new fresh kernel. >> Thank you. Please let me know how it goes. > I don't have any problems with r319091 + patch for "..". > Thank you for testing! -- Andriy Gapon