Thanks for the datapoints.

Yes, the missing disks are missing altogether - e.g. for one filer, most runs report 65 disks, but some report 58. Always seems to the same ones missing.

Frequency wise - it seems to occur about one run in 10 on the system in question.
But, we've not seen it elsewhere, even on systems with over 500 disks.
And more interestingly, the partner head of the system that does it, that is running the same OnTap version, with a similar number of disks, never exhibits the issue.

So something specific to that particular head - but as it's not ours (but one of our customers, just using LogicMonitor to monitor it), we have to rely on him to open a case with netApp.

Thanks


Steve Francis

LogicMonitor Inc

sfrancis@logicmonitor.com
www.logicmonitor.com
Ph: 1 888 41 LOGIC x500
Ph: 1 805 698 0770
My blog: LogicMonitor’s Hosted Monitoring – best support just got better
Twitter Latest tweet: LogicMonitor wins another award: http://t.co/0JzMizx. Thanks!
  Get this email app!  
Signature powered by WiseStamp 


On Wed, Aug 31, 2011 at 8:29 PM, Kevin Graham <kgraham@industrial-marshmallow.com> wrote:

On Aug 26, 2011, at 9:06 AM, Steve Francis wrote:

> Seems to happen more on systems with more disks.
> (e.g. happens semi-regularly on a system running 8.0.2 7-Mode with 60
> odd disks; doesn't happen on systems with less disks.)

Any feel for the frequency? Just ran through a couple dozen iterations on a mix of systems, both DS4243 and DS14mk*'s with 336 to 1152 disks (mostly running 8.0.1P5, though some still back on 7.3.x) and it all came back as expected.

> when using the disk-list-info API command, we sometimes get
> inconsistent info - some disks missing from the list.

Are they missing altogether? Test I ran was just counting size of array from child_get('disk-details')->children_get.