Project roadmap - Revision history

Ilovezfs at 08:14, 30 September 2014

2014-09-30T08:14:39Z

Ilovezfs at 15:31, 3 August 2014

2014-08-03T15:31:13Z

Ilovezfs: /* Medium-term */

2014-08-03T15:27:55Z

‎Medium-term

Ilovezfs at 23:47, 24 July 2014

2014-07-24T23:47:06Z

Ilovezfs at 04:25, 25 April 2014

2014-04-25T04:25:43Z

Ilovezfs: /* .zfs snapshot ctldir fix */

2014-04-16T13:10:02Z

‎.zfs snapshot ctldir fix

Ilovezfs: /* Short-term */

2014-04-16T13:09:50Z

‎Short-term

Ilovezfs: /* zfs_zget race */

2014-04-16T13:05:18Z

‎zfs_zget race

Ilovezfs: /* zfs recv fix */

2014-04-16T12:56:34Z

‎zfs recv fix

Ilovezfs: /* zfs recv panic */

2014-04-16T12:55:24Z

‎zfs recv panic

@@ Line 1: / Line 1: @@
 ==Short-term==
 ===Port ZFS Test Suite from upstream===
@@ Line 31: / Line 38: @@
 * '''Milestone''': 1.3.x
 * '''Blocked by''': /dev/disk#s# device nodes for each ZFS file system.
 ===Handle disk renumbering===

← Older revision		Revision as of 15:31, 3 August 2014
Line 51:		Line 51:
	==Long-term==		==Long-term==
	===GUI===		===GUI===
		+	===More notifications===
		+	* Scrub completed
		+	* Unhealthy zpool status
		+	* Space consumed exceeds 80%
		+	* etc.

← Older revision		Revision as of 15:27, 3 August 2014
Line 10:		Line 10:

	==Medium-term==		==Medium-term==
		+
		+	===Persistent configuration===
		+	* '''Labels''': Enhancement
		+	* '''Description''': Most of the [https://github.com/zfsonlinux/zfs/blob/master/man/man5/zfs-module-parameters.5 ZFS module parameters] offered by ZFS on Linux should be exposed via a plist preference file. Some such options are already available, but only as sysctls, and the configuration is not persistent.
		+	* '''Status''': Not started
		+	* '''Milestone''': 1.3.x
		+	* '''Issue''': https://github.com/openzfsonosx/zfs/issues/149

	===/dev/disk#s# device nodes for each ZFS file system===		===/dev/disk#s# device nodes for each ZFS file system===

@@ Line 1: / Line 1: @@
 ==Short-term==
 ===Port ZFS Test Suite from upstream===
@@ Line 71: / Line 9: @@
 * '''Notes''': Initial work began at the [http://open-zfs.org/wiki/OpenZFS_Developer_Summit OpenZFS Developer Summit Hackathon].
-==Long-term==
+==Medium-term==
 ===/dev/disk#s# device nodes for each ZFS file system===
@@ Line 103: / Line 41: @@
 * '''Blocked by''': [https://github.com/openzfsonosx/zfs/issues/134 Implement the other 57% of vdev_disk.c].
 * '''Notes''': No design decided on yet. ZEVO used the GPT partition UUIDs but this is a non-solution since file vdevs do not have partitions, and because Core Storage does not permit partitioning. It's worth noting that this exact same problem affects ZFS on Linux when the user is relying on /dev/sd[a-z] nodes, which can end up re-lettered when a drive is unplugged and replugged in. This is less of an issue for ZFS on Linux because they have alternate ways of specifying devices (e.g., /dev/disk/by-id) which are unavailable on OS X. We will probably need some sort of equivalent.

@@ Line 100: / Line 100: @@
 * '''Status''': Needs a design
 * '''Milestone''': 1.4.x
-* '''Issue''': https://github.com/openzfsonosx/zfs/issues/104
+* '''Issue''': https://github.com/openzfsonosx/zfs/issues/167
 * '''Blocked by''': [https://github.com/openzfsonosx/zfs/issues/134 Implement the other 57% of vdev_disk.c].
-* '''Notes''': No design decided on yet. ZEVO used the GPT partition UUIDs but this is a non-solution since file vdevs do not have partitions, and because Core Storage does not permit partitioning. Some possible designs are mentioned in https://github.com/openzfsonosx/zfs/issues/104. It's worth noting that this exact same problem affects ZFS on Linux when the user is relying on /dev/sd[a-z] nodes, which can end up re-lettered when a drive is unplugged and replugged in. This is less of an issue for ZFS on Linux because they have alternate ways of specifying devices (e.g., /dev/disk/by-id) which are unavailable on OS X. We will probably need some sort of equivalent.
+* '''Notes''': No design decided on yet. ZEVO used the GPT partition UUIDs but this is a non-solution since file vdevs do not have partitions, and because Core Storage does not permit partitioning. It's worth noting that this exact same problem affects ZFS on Linux when the user is relying on /dev/sd[a-z] nodes, which can end up re-lettered when a drive is unplugged and replugged in. This is less of an issue for ZFS on Linux because they have alternate ways of specifying devices (e.g., /dev/disk/by-id) which are unavailable on OS X. We will probably need some sort of equivalent.

@@ Line 25: / Line 25: @@
 * '''Labels''': Bug
 * '''Description''': Some issues with the .zfs snapshot ctldir following last merge with upstream.
-* '''Status''': Not started.
+* '''Status''': Not started
 * '''Milestone''': 1.2.x

@@ Line 21: / Line 21: @@
 * '''Milestone''': 1.2.1
 * '''Notes''': https://github.com/openzfsonosx/zfs/commit/bfc25a0291a49b71c634a428856318eae82372a4.
 ==Medium-term==

@@ Line 18: / Line 18: @@
 * '''Labels''': Bug
 * '''Description''': <code>vnode_create</code> or <code>vnode_getwithvid</code> must precede <code>ZFS_OBJ_HOLD_EXIT</code> and <code>mutex_exit(&zp->z_lock)</code>.
-* '''Status''': Work in progress
+* '''Status''': Completed
 * '''Milestone''': 1.2.1
-* '''Notes''': Simply moving <code>vnode_create</code> and <code>vnode_getwithvid</code> panics.
+* '''Notes''': https://github.com/openzfsonosx/zfs/commit/bfc25a0291a49b71c634a428856318eae82372a4.
 ==Medium-term==

@@ Line 7: / Line 7: @@
 * '''Milestone''': 1.2.1
-===zfs recv panic===
+===zfs recv fix ===
 * '''Labels''': Bug
 * '''Description''': In the OpenZFS on OS X 1.2.0.dmg release <code>zfs recv -F</code> can panic in some cases.
-* '''Status''': Work in progress
+* '''Status''': Completed
 * '''Milestone''': 1.2.1
-* '''Notes''': No longer panics, but now it hangs in <code>dnode_special_close</code>.
+* '''Notes''': Fixed here https://github.com/openzfsonosx/zfs/commit/6f32f53799bd41ff819901c8f5cdc1d25a6b162e.
 ===zfs_zget race===