Date: Thu, 23 Jan 2014 15:56:17 +0000 From: krad <kraduk@gmail.com> To: Chris Stankevitz <chrisstankevitz@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: ZFS: pool vs FS Message-ID: <CALfReyd4WAF=0_15CDU3j1xaCm49BS0x_6gzBHnevOyeHZGZXQ@mail.gmail.com> In-Reply-To: <CAPi0psvd%2B%2BLdTf_STaAytnNSrwMWsj3dhM8Mho=Wb-XbAWojZw@mail.gmail.com> References: <CAPi0psvd%2B%2BLdTf_STaAytnNSrwMWsj3dhM8Mho=Wb-XbAWojZw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
1. Filesystems, not pools, can be mounted correct pools are imported, however every pool as a root dataset/file system, this is automatically mounted normally to the specified mount point. This isnt necessary the same as the pool name. This may not happen if various filesystem tunables are set (canmount, mountpoint=legacy, jailed,zoned) or import options set (-N -R) 2. "zpool create foo /dev/bar" makes new pool called foo correct, with a root dataset, mounted on $pool_name by default 3. (2) does not create a file system false see (1) 4. After (2), /foo is mounted and ready for writing not always see (1) 5. (4) violates (1) false On 22 January 2014 20:25, Chris Stankevitz <chrisstankevitz@gmail.com>wrote: > Please identify any incorrect statements: > > 1. Filesystems, not pools, can be mounted > > 2. "zpool create foo /dev/bar" makes new pool called foo > > 3. (2) does not create a file system > > 4. After (2), /foo is mounted and ready for writing > > 5. (4) violates (1) > > Thank you, > > Chris > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReyd4WAF=0_15CDU3j1xaCm49BS0x_6gzBHnevOyeHZGZXQ>