Re: [developer] Proposal: Platform-specific ZFS properties

2019-03-26 Thread Gordon Ross
FYI, for NexentaStor we made sharesmb a "no-inherit" property. (because most customers want "traverse mounts" in SMB, meaning the SMB server exposes descendent file systems) Note also that the most common situation (by far) for customer configurations is that a shared ZFS dataset should show up i

[developer] March OpenZFS Leadership Meeting

2019-03-26 Thread Matthew Ahrens
The next OpenZFS Leadership meeting will be held today, March 26, 1pm-2pm Pacific time. Everyone is welcome to attend and participate, and we will try to keep the meeting on agenda and on time. The meetings will be held online via Zoom, and recorded and posted to the website and YouTube after the

Re: [developer] Re: zpool create proposal summary

2019-03-26 Thread Matthew Ahrens
On Mon, Mar 25, 2019 at 10:53 AM Gregor Kopka < mailfrom-openzfs.topicbox@kopka.net> wrote: > Looks good. > > Only thing: *please* make this feature lookup the features for a set *from > a plain text file* (like in /etc/zfs/), just containing > features_name = comma, separated, list, of, featu

Re: [developer] Re: zpool create proposal summary

2019-03-26 Thread Gregor Kopka
> It seems fine, perhaps, to allow __additional__ feature sets this way, but I > think the "portable" family really needs to be something compiled in. The > core value proposition is that "zpool create -o features=portable-2016" is > the same __everywhere__, and allowing it to be easily overrid