Date: Mon, 29 May 2017 13:22:25 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: lev@FreeBSD.org, freebsd-fs@FreeBSD.org Subject: Re: Strange behavior of .zfs/snapshot/* directories in respect to ".." path. Message-ID: <01c59f49-f45a-b02f-31f1-88c130609094@FreeBSD.org> In-Reply-To: <1279842496.20170529132006@serebryakov.spb.ru> References: <1acc5917-f10f-b18a-50e0-84661173e85d@FreeBSD.org> <e7f30e57-a065-dd10-e79a-9a4b770598b6@FreeBSD.org> <1601598008.20170529015948@serebryakov.spb.ru> <8138588b-4b03-16d9-77b6-2a3e3444997d@FreeBSD.org> <1279842496.20170529132006@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01c59f49-f45a-b02f-31f1-88c130609094>