Trevor Watson wrote:
> I don't suppose that there's any chance it could be caused by the 
> disks being powered down could it?

Note that the default retry interval for disks is 60 seconds... sounds like
a plausible explanation.
 -- richard

>
> Neal Pollack wrote:
>> For the last few builds of Nevada, if I come back to my workstation 
>> after
>> long idle periods such as overnight, and try any command that would 
>> touch
>> the zfs filesystem, it hangs for an entire 60 seconds approximately.
>>
>> This would include "ls",  "zpool status", etc.
>>
>> Does anyone has a hint as to how I wold diagnose this?
>> Or is it time for extreme measures such as zfs send to another server,
>> destroy, and rebuild a new zpool?
>>
>> Config and stat:
>> --------------------
>>
>> Running Nevada build 85 and given;
>> # zpool status
>>   pool: tank
>>  state: ONLINE
>>  scrub: none requested
>> config:
>>
>>     NAME        STATE     READ WRITE CKSUM
>>     tank        ONLINE       0     0     0
>>       raidz2    ONLINE       0     0     0
>>         c2d0    ONLINE       0     0     0
>>         c3d0    ONLINE       0     0     0
>>         c4d0    ONLINE       0     0     0
>>         c5d0    ONLINE       0     0     0
>>         c6d0    ONLINE       0     0     0
>>         c7d0    ONLINE       0     0     0
>>         c8d0    ONLINE       0     0     0
>>
>> errors: No known data errors
>>
>>
>> Also given:  I have been doing live upgrade every other build since
>> approx Nevada build 46.  I am running on a Sun Ultra 40 modified
>> to include 8 disks.  (second backplane and SATA quad cable)
>>
>> It appears that the zfs filesystems are running version 1 and Nevada 
>> build 85
>> is running version 3.
>>
>> zbit:~# zfs upgrade
>> This system is currently running ZFS filesystem version 3.
>>
>> The following filesystems are out of date, and can be upgraded.  
>> After being
>> upgraded, these filesystems (and any 'zfs send' streams generated from
>> subsequent snapshots) will no longer be accessible by older software 
>> versions.
>>
>> VER  FILESYSTEM
>> ---  ------------
>>  1   tank
>>  1   tank/arc
>>
>>
>>
>> Any hints at how to isolate and fix this would be appreciated.
>>
>> Thanks,
>>
>> Neal
>>
>>
>>
>> _______________________________________________
>> zfs-discuss mailing list
>> zfs-discuss@opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>   

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to