Date: Thu, 27 Jun 2019 14:21:41 -0700 From: Matthew Ahrens <mahrens@delphix.com> To: developer <developer@open-zfs.org>, illumos-zfs <zfs@lists.illumos.org>, zfs-devel@list.zfsonlinux.org, zfs-devel@freebsd.org, freebsd-fs <freebsd-fs@freebsd.org>, zfs-discuss <zfs-discuss@zfsonlinux.org> Subject: Re: June OpenZFS Leadership Meeting Message-ID: <CAJjvXiHfKA00k2-yxEMVVQqe0dJcQ6H_=AmeuOKJyZ2EGP-Mgw@mail.gmail.com> In-Reply-To: <CAJjvXiGtdTdHWOb7A10=NkV3NXAvwh14yK2gZv%2BLmW9AJF4zMw@mail.gmail.com> References: <CAJjvXiE%2B27fYZh-RUmE=mjD4N63TrnTQVb65qaPZDj4K6oS-Rg@mail.gmail.com> <CAJjvXiE7y%2BYXAZCewDKNKXCmvMYhh4Fy0wt8Kh8V21WvYz3opg@mail.gmail.com> <CAJjvXiHhhZcg_4Ju1U1F9UWRxbNyJyDdnxp89CnBCQpWvqO4xw@mail.gmail.com> <CAJjvXiG4xB76c5p6OVmu9-zVz47DCcmPs%2BT0TUvMf572WXtNxw@mail.gmail.com> <CAJjvXiGXzxu0KiJ1eEHpcpM_o-L6zK-Kd=J2QjXC2wQsMR3Szg@mail.gmail.com> <CAJjvXiEE9beZ1fa8ug3SOExZLS6zkprCn%2BYaZRaKb-3WYAo7zA@mail.gmail.com> <CAJjvXiGtdTdHWOb7A10=NkV3NXAvwh14yK2gZv%2BLmW9AJF4zMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At this week's meeting we discussed FreeBSD/ZoL integration; error reporting infrastructure; and using pyzfs to get zpool config information. The video recording is now posted: https://www.youtube.com/watch?v=3DTJwykiJmH0M The next meeting will be at 11am US/Pacific on July 23rd. Full notes below: - FreeBSD / ZoL integration update - Goal: Single repo that builds for both platforms - https://github.com/zfsonfreebsd/ZoF/tree/projects/zfsbsd/module - Goal is for FreeBSD 13 to use ZoF by default (but may slip to FreeBSD 14) - Goal to get it into current repo around end of September? - Jorgen: Where should I direct Windows/OSX questions? (#openzfs or ZoL Developer list) - Do a PR for additional platforms/tree for additional platforms - Change zfsonlinux/zfs =3D> openzfs/zfs. Brian & Matt will come up wit= h a proposal for naming and structure that reflects what developers do/= use - Announcements of big, long-standing projects being available: - Linux - Redacted send/recv merged! - Illumos - ZFS crypto landed! - Discuss error reporting (Tom) - Do we want to move to something more general (e.g., have the kernel return strings)? - Continue to extend zfs_errno_t, though this doesn=E2=80=99t help prov= ide additional context/information, and then add new strings for user - pyzfs PR <https://github.com/zfsonlinux/zfs/pull/8956>; (Richard E) - Specifically how to get the pool config info programmatically - Programmatic =E2=80=9Czpool status=E2=80=9D that is retrievable, and = any time you add something to zpool you need to make sure status continues to be retrievable. (some mistake that Joshua pointed out...) - Translation of the config to a stable nvlist? Not sure if this should be in libzfs_core or the kernel. Kernel is better but might ignore backward compatibility. - Newer version of userland continue to work without rebooting the kernel. - Could a spanning mode option be added for multi-vdev zpools instead of the default striping data across all vdevs? The intent is to prioritize data integrity over access speed for large archival / backup pools, and = a workaround with multiple pools joined with mergerfs seems suboptimal if = the LOE of adding support for this is low. (Guirara DaiKaiju) - Matt: I think you=E2=80=99re suggesting that `zpool create disk1 disk= 2 =E2=80=A6` create the pool as a mirror, as though you typed `zpool create mirror disk1 disk 2 =E2=80=A6`. And perhaps that `zpool add=E2=80=A6` should inst= ead do `zpool attach =E2=80=A6`. On Tue, Jun 25, 2019 at 9:56 AM Matthew Ahrens <mahrens@delphix.com> wrote: > The next OpenZFS Leadership meeting will be held today, June 25, 1pm-2pm > Pacific time. We don't have much on the agenda for this month, so if the= re > are things you'd like to discuss, this is a good opportunity - send me an > email or edit the doc :) > > Everyone is welcome to attend and participate, and we will try to keep th= e > 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 meeting. > > The agenda for the meeting will be a discussion of the projects listed in > the agenda doc. > > For more information and details on how to attend, as well as notes and > video from the previous meeting, please see the agenda document: > > > https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnW= HhV-BM/edit > > > <https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAn= WHhV-BM/edit> > --matt >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJjvXiHfKA00k2-yxEMVVQqe0dJcQ6H_=AmeuOKJyZ2EGP-Mgw>