Gabriele, There was a fix for this already put into s10. So assuming you have that fix, the read block limits command failed during initialization. This could happen for a number of reasons (drive specific).
You might try and load the drive and have it completely ready before the OS discovers it. Randy Larry Liu wrote: > Gabriele Bulfon 写道: > >> Do you know any way to workaround the bug before the update? >> thx >> >> > I don't know any. I guess it could be avoided if you don't use ioctl > MTIOCTOP with option MTSRSZ. I didn't find any MTSRSZ (set record size) > in any tape command, like mt, tar, cpio, etc. > > You mentioned you could reproduce the problem by manual command. I am > wondering how? Could you please provide the steps? > > Or, it is Bacula, which is using that ioctl, I would suggest you use > solaris tape command (mt, tar, cpio, dd, etc.) instead on your Tandberg > tape drive before the patch is released. > > Larry > >> Hi Gabriele, >> >> There was a bug in solaris can cause the panic. You will see the >> fix in >> s10 update 4. >> >> > > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
