Hello,
While destroying a dataset, sometimes ZFS kind of hangs the machine. I
imagine it''s starving all I/O while deleting the blocks, right ?
Here logbias=latency, the commit interval is the default (30 seconds) and
we have SSDs for logs and cache.
Is there a way to "slow down" the destroy a little bit in order to
reserve
I/O for NFS clients ? Degraded performance isn''t as bad as total loss
of
availability our case.
I was thinking we could set logbias=throughput and decrease the commit
interval to 10 seconds to keep it running more smoothly.
Here''s the pool configuration. Note the 2 slogs devices.. they were
supposed to be a mirror but got added by mistake.
NAME STATE READ WRITE CKSUM
trunk ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t4d0 ONLINE 0 0 0
c7t5d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t6d0 ONLINE 0 0 0
c7t7d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t8d0 ONLINE 0 0 0
c7t9d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t10d0 ONLINE 0 0 0
c7t11d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t12d0 ONLINE 0 0 0
c7t13d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t14d0 ONLINE 0 0 0
c7t15d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t16d0 ONLINE 0 0 0
c7t17d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t18d0 ONLINE 0 0 0
c7t19d0 ONLINE 0 0 0
mirror ONLINE 0 0 0
c7t20d0 ONLINE 0 0 0
c7t21d0 ONLINE 0 0 0
logs ONLINE 0 0 0
c7t1d0 ONLINE 0 0 0
c7t2d0 ONLINE 0 0 0
cache
c7t22d0 ONLINE 0 0 0
spares
c7t3d0 AVAIL
Any ideas?
Thank you,
--
Giovanni Tirloni
sysdroid.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100226/dc5c4d62/attachment.html>