[developer] Re: [openzfs/openzfs] 8648 Fix range locking in ZIL commit codepath (#462)

2017-09-14 Thread Igor K
reproduced on VMware VM: ``` root@dilos-test:~# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c2t0d0 /pci@0,0/pci15ad,7a0@15/pci15ad,7c0@0/disk@0,0 1. c2t1d0 /pci@0,0/pci15ad,7a0@15/pci15ad,7c0@0/disk@1,0 2. c2t2d0

[developer] Re: [openzfs/openzfs] 8648 Fix range locking in ZIL commit codepath (#462)

2017-09-14 Thread Igor K
@prakashsurya we are using iSCSI setup. 3 targets with raidz1 = 6drives. 1 initiator - where we have attached drives from targets and created zpool based on iSCSI drives from targets. pool: tstpool3 id: 3733871914129874332 state: ONLINE action: The pool can be imported using its name

[developer] Re: [zfs] ZIO_IOCTL_PIPELINE excludes ZIO_STAGE_VDEV_IO_DONE

2017-09-14 Thread George Wilson
Andriy, The ZIO_STAGE_VDEV_IO_DONE is not necessary for ZIO_IOCTL_PIPELINE and that's why it was removed. At least in illumos, there is no functional reason for calling it. To add it back would require a small amount of change which should not be a big deal. Can you provide some context around

[developer] Re: [openzfs/openzfs] 8652 Tautological comparisons with ZPROP_INVAL (#466)

2017-09-14 Thread Alan Somers
lint errors fixed and squashed. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/466#issuecomment-329521422 -- openzfs-developer Archives:

[developer] ZIO_IOCTL_PIPELINE excludes ZIO_STAGE_VDEV_IO_DONE

2017-09-14 Thread Andriy Gapon
Does anyone know why ZIO_IOCTL_PIPELINE does not include ZIO_STAGE_VDEV_IO_DONE? Or, in other words, why ZIO_IOCTL_PIPELINE actively excludes it by not using ZIO_VDEV_IO_STAGES? It seems that ZIO_IOCTL_PIPELINE had ZIO_VDEV_IO_STAGES until this commit: > commit