Brian Behlendorf 5ce3b77ef8 Remove /zvol/ path component for zvol devices ... As part of commit f162433deb the /zvol/ path component was added for zvol devices. This ensured all zvol devices would be created by udev in /dev/zvol/<pool>/<dataset>, as opposed to the previous /dev/<pool>/<dataset> path. Logically, it was nice to organize them in a directory much like Solaris does. However, while initial testing showed this to work fine with modern kernels it does not appear to be supported under RHEL5. The extra path component triggers a NULL deref in create_dir(). Anyway, to avoid having different zvol path names based on your kernel version its more consistent simply to revert to the original naming convention. If you really want the zvol component you can always add custom udev rules to do exactly this. We can revisiting this change again once we are willing to drop support for RHEL5 and similar older distros.		2010-08-09 16:42:42 -07:00
..
sys/fs	Remove /zvol/ path component for zvol devices	2010-08-09 16:42:42 -07:00
zfs_comutil.h	Update core ZFS code from build 121 to build 141.	2010-05-28 13:45:14 -07:00
zfs_deleg.h	Rebase master to b121	2009-08-18 11:43:27 -07:00
zfs_fletcher.h	Update core ZFS code from build 121 to build 141.	2010-05-28 13:45:14 -07:00
zfs_namecheck.h	Rebase master to b117	2009-07-02 15:44:48 -07:00
zfs_prop.h	Update core ZFS code from build 121 to build 141.	2010-05-28 13:45:14 -07:00