On Tue, 29 Apr 2008, Krzys wrote: > I am not sure, I had very ok system when I did originally build it and when I > did originally started to use zfs, but now its so horribly slow. I do believe > that amount of snaps that I have are causing it.
This seems like a bold assumption without supportive evidence. > # zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > mypool 278G 255G 23.0G 91% ONLINE - > mypool2 1.59T 1.54T 57.0G 96% ONLINE - Very full! > For example I am trying to copy 1.4G file from my /var/mail to /d/d1 directory > which is zfs file system on mypool2 pool. It takes 25 minutes to copy it, > while > copying it to tmp directory only takes few seconds. Whats wrong with this? Why > its so long to copy that wile to my zfs file system? Not good. Some filesystems get slower when they are almost full since they have to work harder to find resources and verify quota limits. I don't know if that applies to ZFS. However, it may be that you have one or more disks which is experiencing many soft errors (several re-tries before success) and maybe you should look into that first. ZFS runs on top of a bunch of other subsystems and drivers so if those other subsystems and drivers are slow to repond then ZFS will be slow. With your raidz2 setup, all it takes is one slow disk to slow everything down. I suggest using 'iostat -e' to check for device errors, and 'iostat -x' (while doing the copy) to look for suspicious device behavior. Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
