Date: Sun, 24 Aug 2014 12:56:42 -0400 From: Paul Kraus <paul@kraus-haus.org> To: Scott Bennett <bennett@sdf.org> Cc: freebsd-questions@freebsd.org Subject: Re: some ZFS questions Message-ID: <022EBB92-5E27-4198-8FD7-1B00B35E5D50@kraus-haus.org> In-Reply-To: <201408241019.s7OAJoBw025610@sdf.org> References: <201408070816.s778G9ug015988@sdf.org> <53E3A836.9080904@my.hennepintech.edu> <201408080706.s78765xs022311@sdf.org> <D3447347-512D-4DFF-BC4A-8ECE5B77F3D4@kraus-haus.org> <201408211033.s7LAXWbN006985@sdf.org> <FE57A90F-8783-40E1-A3FF-08867129CFA4@kraus-haus.org> <201408241019.s7OAJoBw025610@sdf.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 24, 2014, at 6:19, Scott Bennett <bennett@sdf.org> wrote: > Paul Kraus <paul@kraus-haus.org> wrote: >> When you create a zpool you get both the zpool and a zfs dataset of = the same name. You can use this dataset, but if I am going to be = creating *any* other datasets in this zpool I do not. I only use = hierarchical datasets in very specific ways as there are rules on = inheritance and mount points. For example: >>=20 > Oh. I hadn't gleaned that from the man pages or other = documentation. > Thanks for pointing it out. It is not very obvious, and the downsides are decidedly not obvious. I = learned to do what I now do through trail and error and many painful = reconfigurations over the years. The biggest thing to watch out for is = hidden (non-obvious) dependencies due to the hierarchical nature of = datasets created within (on top of ?) other datasets.=20 -- Paul Kraus paul@kraus-haus.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?022EBB92-5E27-4198-8FD7-1B00B35E5D50>