Date: Fri, 22 Jul 2016 07:26:35 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org>, freebsd-fs@FreeBSD.org Subject: Re: ZFS snapshot automount -- not creating '..' directory links correctly? Message-ID: <83e4c7de-9d35-e995-52bc-f2a5cce3ad46@FreeBSD.org> In-Reply-To: <e6e781c4-0a06-6736-d0be-2fb269e5b3fc@FreeBSD.org> References: <c426d60a-88af-6297-d99b-be9d7ac90661@freebsd.org> <e6e781c4-0a06-6736-d0be-2fb269e5b3fc@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --S0kjLDHsKUO2h8HIhQaPRAIMGGHTM89qR Content-Type: multipart/mixed; boundary="Fl9oIOk4hWPgJ1F5Lxnqc4d8vvSGVMSBa" From: Matthew Seaman <matthew@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org>, freebsd-fs@FreeBSD.org Message-ID: <83e4c7de-9d35-e995-52bc-f2a5cce3ad46@FreeBSD.org> Subject: Re: ZFS snapshot automount -- not creating '..' directory links correctly? References: <c426d60a-88af-6297-d99b-be9d7ac90661@freebsd.org> <e6e781c4-0a06-6736-d0be-2fb269e5b3fc@FreeBSD.org> In-Reply-To: <e6e781c4-0a06-6736-d0be-2fb269e5b3fc@FreeBSD.org> --Fl9oIOk4hWPgJ1F5Lxnqc4d8vvSGVMSBa Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 21/07/2016 11:50, Andriy Gapon wrote: > On 21/07/2016 12:42, Matthew Seaman wrote: >> Hi, >> >> Ever since I upgraded to 11.0-BETA1, my tarsnap backups have been >> misbehaving. While corresponding with Colin, and trying to diagnose t= he >> problem I discovered that there seems to be a problem with the '..' li= nk >> in an automounted snapshot. >> >> It's easy to reproduce: >> >> # zfs create zroot/empty >> # zfs snapshot zroot/empty@20160721-1011 >> >> # cd /empty/.zfs/snapshot/20160721-1011 >> # stat -f "%N: %HT%SY" \ >> /empty /empty/.zfs /empty/.zfs/snapshot \ >> /empty/.zfs/snapshot/20160721-1011 . .. >> /empty: Directory >> /empty/.zfs: Directory >> /empty/.zfs/snapshot: Directory >> /empty/.zfs/snapshot/20160721-1011: Directory >> .: Directory >> stat: ..: stat: Not a directory >> >> This is on: >> >> # uname -a >> FreeBSD lucid-nonsense.infracaninophile.co.uk 11.0-BETA1 FreeBSD >> 11.0-BETA1 #2 r302482: Sat Jul 9 15:37:08 BST 2016 >=20 > This is fixed in 302994. > Sorry about the breakage. >=20 >> root@lucid-nonsense.infracaninophile.co.uk:/usr/obj/usr/src/sys/GENERI= C >> amd64 >> >> Attempting the same test on a 10.3-STABLE machine returned '..' as a >> directory perfectly happily. Thanks for that. I upgraded and now my backups are working properly agai= n. Cheers, Matthew --Fl9oIOk4hWPgJ1F5Lxnqc4d8vvSGVMSBa-- --S0kjLDHsKUO2h8HIhQaPRAIMGGHTM89qR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXkbybXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATiIYP/0oBxH0vbKg86XAewpBUamaf xaZcuI8tClLMSdVRFR64NU3Z3GuejiHWoj1ajMzD1pw8O1tsH/xpNzD8IBNjfRyz YGMlEQEIOUwcC+XyI4CHkN/4A3rQIn2wMutbHMecXYTN46TXHvCdNDsAaqie+E// N4wFZPfVMivA0Rc9WJ7EGdBoiK/L26bS+82jHplhHYnB3yLZ19iSNdx4SFWHfb9h zN9pZ7aHIT7DsfQlVpUVxSb1z7+EVfK7F3dwoR0ohP6MaaJWVmPAYTBs5WCE1B57 W2n6zwowluohRQ7AUKzI0kxyHSrBHO7ifftsajGrKXPV0ils30pX6c+am53SEQz2 qwSJuzXTczWA5jis3zTabvpdb2YFsNR9JRcepXud/O7aY8VGgZvEKbUDRyk774vY jX7t9eJsVA9cBZMz5zlhjPTvkW0YHLz7of+We77H2VTwxBYW3/g4tM2CqpQy9ta+ e/fzu3GoHyQ9OIH4Bk2U2qRauQHHev+Q0o+GO1Ev1sokcdrZ3MEhudSkquOF/XIA ah3rY8c86fWO4tZiERlZ1tnuQ3dR7paCy1ABRAYKovb3PACPw3qC2VUDdYqhA6g5 F6GHObGA5s/yl3wQ70ax9wg0NL9ANzYPL33SptwdWdVwBPQpD1IxJUTC4K3UH12h 4pCyixKsuQ7xnJyXdbB2 =MDu3 -----END PGP SIGNATURE----- --S0kjLDHsKUO2h8HIhQaPRAIMGGHTM89qR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83e4c7de-9d35-e995-52bc-f2a5cce3ad46>