I've been seeing read and write performance pathologies with Linux
ext3 over iSCSI to zvols, especially with small writes. Does running
a journalled filesystem to a zvol turn the block storage into swiss
cheese? I am considering serving ext3 journals (and possibly swap
too) off a raw, hardware-mirr
[EMAIL PROTECTED] wrote on 17/07/2007 02:36:06 PM:
> Running Solaris 10 Update 3 on an X4500 I have found that it is possible
> to reproducibly block all writes to a ZFS pool by running "chgrp -R"
> on any large filesystem in that pool. As can be seen below in the zpool
> iostat output below, aft
[EMAIL PROTECTED] wrote on 17/07/2007 05:12:49 AM:
> I'm going to be setting up about 6 virtual machines (Windows &
> Linux) in either VMWare Server or Xen on a CentOS 5 box. I'd like to
> connect to a ZFS iSCSI target to store the vm images and be able to
> use zfs snapshots for backup. I have
I've been saving up a few wishlist items for zfs. Time to share.
1. A verbose (-v) option to the zfs commandline.
In particular zfs sometimes takes a while to return from zfs snapshot -r
tank/[EMAIL PROTECTED] in the case where there are a great many iscsi shared
volumes underneath. A little pr
