Impossible to answer because we lack all the information. Queue length in general is totalyl useless as a counter - subsytems can have large queues without getting slow.
There is another set of cuotners which says seconds / read or seconds / write. This (*1000 to get milliseconds) is mrore usefull. I dont care how long the queue is - i care when I overlaod the drive which is when the response time gets slower.
It is a misconception that people think queue length without a LO of interpretation and additional inforamtion is usefull.
Want an extreme? I know of a sql server having 255length disc queue.... to every of itÄs nearly 30 discs. It has 30 discs to be able to put in larger total queues as thje drivers only allow 255 maxium for one disc.
Bad? well, the uplink is multiple 8 gigabit fibrechannels to a 160 disc HP EVA SAN with 32 gigabyte cache. Response time is STILL1-2 milliseconds ith those queue lengths. SO, the length is totally useless here. The seconds / x gives an imediate answerable number without a lot of interpretation.
Update: if that is hat you asy- single disc, probably SATA, then yes, the lenghts are way too high, your IO is tottaly overloaded.