Just to let everybody know, I'm in touch with Charles and we're working on this problem offline. We'll report back to the list when we've got something to talk about.
James On Wed, 14 Jan 2009 08:37:44 -0800 (PST) Charles Wright <char...@asc.edu> wrote: > Here's an update: > > I thought that the error message > arcmsr0: too many outstanding commands > might be due to a Scsi queue being over ran > > The areca driver has > #*define* ARCMSR_MAX_OUTSTANDING_CMD > <http://src.opensolaris.org/source/s?defs=ARCMSR_MAX_OUTSTANDING_CMD> > 256 > > What might be happening is each raid set results in a new instance of > the areca driver getting loaded so perhaps the scsi queue on the card > is just get over ran as each drive is getting a queue depth of 256, > as such I tested with sd_max_throttle:16 > > (16 Drives * 16 Queues = 256) > > I verified sd_max_throttle got set via: > r...@yoda:~/solaris-install-stuff# echo "sd_max_throttle/D" |mdb -k > sd_max_throttle: > sd_max_throttle:16 > James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
