Can you make the crash dumps available? I only see text output
attached to the bug.
You find it under:
http://images.firmos.at/download/crash_zfs_send/vmdump.0
http://images.firmos.at/download/crash_zpool_create/vmdump.0
We simulated the bug using VMware Fusion on a Mac,
but it is the same as on the datacenter hardware.
Any particular reason that you're creating a pool on top of an iscsi
device which is backed by a zvol on a pool on the same machine? Have
you tried it using 2 different machines?
Yes it has an economical reason, we have a setup with two rather
expensive servers.
(Dual E5-2680, 256GB RAM, 6 Disk Chassis ZEUS RAM Drive for ZIL)
The SAS disks are arranged in a zpool with RAIDZ2 vdevs. This pool
exports a large ZVOL as a LUN via FC.
A mirror of two LUNs form a synchronous mirrored pool, one LUN is local
on the same server and one remote on the other location.
The pool is imported on exclusively one machine and can be transparently
failovered for a VMWare Host that imports via NFS doing forced sync writes.
Everything works very well, performance is very good (not comparable to
async replication alone, but with high availability)
Alone when we "ZFS send" a snapshot to a backup system the problem occurs.
In the mirrored pool in the datacenter, the "zfs send" hangs also until
timeouts on the local provided LUN occur
and the mirrored pool took the local LUN offline.
A design with 2 machines on each location(one with the diskpool, and one
with the mirrored pool) is tested and works -
but if the mentioned problem would not occur we could save power, costs
and rackspace.
Is there a reason why this setup would be a bad idea, or are we just
hitting something no one has tried before?
Thx,
Franz
_______________________________________________
developer mailing list
[email protected]
http://lists.open-zfs.org/mailman/listinfo/developer
