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
On 27 March, 2008 - Neal Pollack sent me these 1,9K bytes:> 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.Umm. nevada 78 is at version 10.. so I don''t think you''ve managed to upgrade stuff 100% ;) This system is currently running ZFS pool version 10. The following versions are supported: VER DESCRIPTION --- -------------------------------------------------------- 1 Initial ZFS version 2 Ditto blocks (replicated metadata) 3 Hot spares and double parity RAID-Z 4 zpool history 5 Compression using the gzip algorithm 6 bootfs pool property 7 Separate intent log devices 8 Delegated administration 9 refquota and refreservation properties 10 Cache devices For more information on a particular version, including supported releases, see: http://www.opensolaris.org/os/community/zfs/version/N /Tomas -- Tomas ?gren, stric at acc.umu.se, http://www.acc.umu.se/~stric/ |- Student at Computing Science, University of Ume? `- Sysadmin at {cs,acc}.umu.se
Tomas ?gren wrote:> On 27 March, 2008 - Neal Pollack sent me these 1,9K bytes: > > >> 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. >> > > Umm. nevada 78 is at version 10.. so I don''t think you''ve managed to > upgrade stuff 100% ;) > > This system is currently running ZFS pool version 10. >"ZFS" filesystem version is at "3" My zpool is at version "10" zbit:~# zpool upgrade This system is currently running ZFS pool version 10. All pools are formatted using this version.> The following versions are supported: > > VER DESCRIPTION > --- -------------------------------------------------------- > 1 Initial ZFS version > 2 Ditto blocks (replicated metadata) > 3 Hot spares and double parity RAID-Z > 4 zpool history > 5 Compression using the gzip algorithm > 6 bootfs pool property > 7 Separate intent log devices > 8 Delegated administration > 9 refquota and refreservation properties > 10 Cache devices > For more information on a particular version, including supported > releases, see: > > http://www.opensolaris.org/os/community/zfs/version/N > > > /Tomas >
I don''t suppose that there''s any chance it could be caused by the disks being powered down could it? 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 at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3253 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080328/8bfdc5a2/attachment.bin>
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 at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > ------------------------------------------------------------------------ > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >