Re: star quitting when changing tapes - FIXED!!!!
Dan <[email protected]> Mon, 10 Jul 2006 17:58:59 -0700 (PDT)
| Newsgroups | gmane.comp.archivers.star.user |
|---|---|
| Message-ID | <[email protected]> |
The bug in the Linux kernel that kills star when backing up to multiple tapes is fixed in the latest series of kernels! Here's the list: Linux kernel: 2.6.15.x - WORKS FINE 2.6.16.x - BROKEN 2.6.17.x - WORKS FINE The README in the star distribution should probably be updated to let users know about this kernel bug. Thanks for your help, Joerg. -Dan Joerg Schilling <[email protected]> wrote: Dan wrote: > open("/dev/nst0", O_RDWR|O_CREAT|O_LARGEFILE, 0666) = 4 > fcntl64(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) > fstat64(4, {st_mode=S_IFCHR|0660, st_rdev=makedev(9, 128), ...}) = 0 > ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfa0b804) = -1 EINVAL (Invalid argument) > > Joerg, can you point me to where in the code this ioctl is sent? A kernel guy I emailed said this might be sending something that's screwing up the new st.c driver. If this is causing an error to occur (REQUEST SENSE, ASC/ASCQ kind of error), the driver won't know about it until the next I/O is done. At that point, the driver will block waiting for someone to read the additional error codes, thus causing the EBUSY. I know EBUSY should never happen on a write(2), and he agrees. I need to do more troubleshooting, and disabling this ioctl command is the first step. I would guess this is a call to isatty() from within stdio. BTW: the correct error code for a non-tty fd would be ENOTTY. --------------------------------- Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail Beta.