> Thus far there is no evidence that there is anything wrong with your
> storage arrays, or even with zfs. The problem seems likely to be
> somewhere else in the kernel.
Agreed. And I tend to think that the problem lays somewhere in the LDOM
software. I mainly just wanted to get some experience
On Tue, 19 Jan 2010, Scott Duckworth wrote:
No errors reported on any disks.
Nothing sticks out in /var/adm/messages on either the primary or cs0 domain.
Thus far there is no evidence that there is anything wrong with your
storage arrays, or even with zfs. The problem seems likely to be
som
No errors reported on any disks.
$ iostat -xe
extended device statistics errors ---
devicer/sw/s kr/s kw/s wait actv svc_t %w %b s/w h/w trn tot
vdc0 0.65.6 25.0 33.5 0.0 0.1 17.3 0 2 0 0 0 0
vdc1 78.1 24.4
On Tue, 19 Jan 2010, Scott Duckworth wrote:
[Cross-posting to ldoms-discuss]
We are occasionally seeing massive time-to-completions for I/O
requests on ZFS file systems on a Sun T5220 attached to a Sun
StorageTek 2540 and a Sun J4200, and using a SSD drive as a ZIL
device. Primary access to
On Tue, Jan 19, 2010 at 02:24:11PM -0800, Scott Duckworth wrote:
> [Cross-posting to ldoms-discuss]
>
> We are occasionally seeing massive time-to-completions for I/O
> requests on ZFS file systems on a Sun T5220 attached to a Sun
> StorageTek 2540 and a Sun J4200, and using a SSD drive as a ZIL
>
[Cross-posting to ldoms-discuss]
We are occasionally seeing massive time-to-completions for I/O requests on ZFS
file systems on a Sun T5220 attached to a Sun StorageTek 2540 and a Sun J4200,
and using a SSD drive as a ZIL device. Primary access to this system is via
NFS, and with NFS COMMITs b
