Hello Robert, Monday, April 23, 2007, 10:44:00 PM, you wrote:
RM> Hello Peter, RM> Monday, April 23, 2007, 9:27:56 PM, you wrote: PT>> On 4/23/07, Robert Milkowski <[EMAIL PROTECTED]> wrote: >>> >>> Relatively low traffic to the pool but sync takes too long to complete >>> and other operations are also not that fast. >>> >>> Disks are on 3510 array. zil_disable=1. >>> >>> >>> bash-3.00# ptime sync >>> >>> real 1:21.569 >>> user 0.001 >>> sys 0.027 PT>> Hey, that is *quick*! PT>> On Friday afternoon I typed sync mid-afternoon. Nothing had happened PT>> a couple of hours later when I went home. It looked as though it had finished PT>> by 11pm, when I checked in from home. PT>> This was on a thumper running S10U3. As far as I could tell, all writes PT>> to the pool stopped completely. There were applications trying to write, PT>> but they had just stopped (and picked up later in the evening). A fairly PT>> consistent few hundred K per second of reads; no writes; and pretty low PT>> system load. PT>> It did recover, but write latencies of a few hours is rather undesirable. PT>> What on earth was it doing? RM> I've seen it too :( RM> Other that that I can see that while I can observe reads and writes RM> zfs is issuing write cache flush commands even in minutes instead of RM> 5s default. And nfsd goes crazy then. RM> Then zfs commands like zpool status, zfs list, etc. can hung for RM> hours... nothing unusual with iostat. Also stopping nfsd can take dozen of minutes to complete. I've never observed this with nfsd/ufs. -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
