From owner-freebsd-fs@freebsd.org Tue Jul 7 13:18:05 2015 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 9EA1C995E1F for ; Tue, 7 Jul 2015 13:18:05 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30D6B1885 for ; Tue, 7 Jul 2015 13:18:05 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by wgbgr6 with SMTP id gr6so13831232wgb.3 for ; Tue, 07 Jul 2015 06:18:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZRP2OFffz9Oo0KAbHlOnBNWplV4iJj2sprGGIoqV7is=; b=CC8CZcZnjEg6g5aGNhcegT6QYgtzpOxEvsVxPW6kKyZbGDcbILjJp66R1Ji6YeJ3sg eqtI2MY+ZHBqBn0OGWD2jy6i+FVD8XTTEwlWgA0qAyLpI/G3rD6hjyUlnUpw/iC+VcDe W9SkezXYBot83P4WVtOM5uDzxUpr4EeIXKqqmdec4mNNBbjqmtjZkZ/Zw7D7HTGcZRkL HpxnLPZXjVR6guwKbG6ODzJXBaVKim0+UJv9IJ42+ewMU9L+LrjOcMhRqR92//7Ge9lR sFTFmDPWg0YXPA2UbEMyayZnb5B2k9d8/I5GJ00ZpJ4GFLKNOUzLgHfiew9qIxQdWlRx ZYqQ== MIME-Version: 1.0 X-Received: by 10.180.104.197 with SMTP id gg5mr102980064wib.27.1436275081650; Tue, 07 Jul 2015 06:18:01 -0700 (PDT) Received: by 10.180.73.5 with HTTP; Tue, 7 Jul 2015 06:18:01 -0700 (PDT) In-Reply-To: References: <5599496C.6010702@sneakertech.com> <20150705210306.GA1048@in-addr.com> <559A08AF.9050809@sneakertech.com> <559A14DB.3080905@sneakertech.com> Date: Tue, 7 Jul 2015 14:18:01 +0100 Message-ID: Subject: Re: A question about ZFS built-in SMB From: krad To: Freddie Cash Cc: Quartz , FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2015 13:18:05 -0000 "but it's the 3rd party nfs server that actually does the sharing." You are misrepresenting here a little as the nfs server in freebsd is a core part of the OS, and not some third party addon. It has a few userland daemons that can be used however its mostly in kernel. Linux is pretty much the same as well. However the key difference between Freebsd and linux is that because no mainstream linux distro ships with production grade zfsonlinux there has been little work on the userland integration in comparison to solaris, so stuff like the auto configuration of nfs isn't always there yet. Samba is a 3rd part product for freebsd and linux though explaining why there isn't any auto configuration. freebsd # kldstat -v | grep nfs 208 nfslockd 158 nfscommon 207 nfssvc 161 nfsd 159 nfs 179 acl_nfs4 160 nfscl 206 nfslock Linux [cscott@SL1VSIKS ~]$ lsmod | grep nfs nfsd 299008 13 auth_rpcgss 61440 1 nfsd nfs_acl 16384 1 nfsd lockd 94208 1 nfsd grace 16384 2 nfsd,lockd sunrpc 327680 19 nfsd,auth_rpcgss,lockd,nfs_acl On 6 July 2015 at 15:19, Freddie Cash wrote: > On Jul 5, 2015 10:40 PM, "Quartz" wrote: > >> > >> No, actually, it isn't. :) It works in a similar manner to sharenfs on > >> FreeBSD. You still require a separate NFS server installed, and ask it > >> does it copy the info to an exports file. > >> > >> Similar for sharesmb. You still require Samba being installed on Linux. > >> All the property does is add the filesystem to a separate smb config > >> file (or something like that; never actually used it on Linux). > >> > >> You still require the NFS and SMB packages installed for your distro. > >> Same as you would for any other FS on Linux. > > > > > > > > So I'm a little confused here. > > > > On Linux, the property is active and usable but only creates the share, > meaning you still need the sever software to host it. On FreeBSD, the > property doesn't work at all, and you need the server software to do > everything...... > > Correct. > > On Solaris derivatives, you only need the OS installed and ZFS configured > in order to share filesystems via the share{nfs|smb} properties. They have > in-kernel NFS and CIFS servers. No 3rd party software required, the zfs > system does everything. > > On Linux, you need the OS, ZFS, an NFS server, and Samba installed in order > to share filesystems. You can use the share{nfs|smb} properties to > configure the shares, but it's 3rd party software (external to zfs) that > actually does the sharing. > > On FreeBSD, you need the OS, ZFS, an NFS server, and Samba installed in > order to share filesystems. You can use the sharenfs property to configure > an nfs share, but it's the 3rd party nfs server that actually does the > sharing. And you need to do everything manually via samba to share > filesystems as the sharesmb property isn't supported. > > Or, you can just ignore the share{nfs|smb} properties and do everything > manually, the way you would for any filesystem. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >