Thanks for your help, Carl and Andrew. Below is output results from: ls -l /dev/st0* crw-rw---- 1 root disk 9, 0 Aug 7 10:30 /dev/st0 crw-rw---- 1 root disk 9, 96 Aug 7 10:30 /dev/st0a crw-rw---- 1 root disk 9, 32 Aug 7 10:30 /dev/st0l crw-rw---- 1 root disk 9, 64 Aug 7 10:30 /dev/st0m
The same as your emailed results. mt -f /dev/st0 status /dev/st0: Device or resource busy This is the same result as before, either with an action or with a non-action command. I'm a member of group "Disk" and the same results occur as when I'm logged into as root. Incidentally, Bacula is also a member of group "Disk." I'm obviously missing something, but can figure it out. Any suggestions would be great. Regards, Brian Butler -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carl Lowenstein Sent: Tuesday, August 08, 2006 1:02 PM To: Main Discussion List for KPLUG Subject: Re: Sony SDT-9000 SCSI Tape Drive Problems On 8/8/06, Andrew Lentvorski <[EMAIL PROTECTED]> wrote: > Brian Butler wrote: > > > Attached devices: > > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > > Vendor: 3ware Model: Logical Disk 0 Rev: 1.2 > > Type: Direct-Access ANSI SCSI revision: ffffffff > > Host: scsi5 Channel: 00 Id: 02 Lun: 00 > > Vendor: SONY Model: SDT-9000 Rev: 0400 > > Type: Sequential-Access ANSI SCSI revision: 02 > > > > In my messages file in /var/log/ I'm getting the following: > > > > kernel: st0: MTSETDRVBUFFER only allowed for root > > > > I don't know how to resolve this problem. Any assistance would be > > appreciated. > > Well, I'm going to ask the obvious since you didn't cut and paste your > prompts: > > Are you logged in as root when you execute the mt commands? > > Tape drives often have unusual permissions on their /dev entries. In > addition, for devfs I seem to recall that you have to edit some file to > set the permissions rather than doing a direct chmod on the entry. > > Another question along the same line of inquiry: is the "mt" command aliased to something else? Have you tried the non-action command mt -f /dev/st0 status Have you looked at the permissions of /dev/st0? [EMAIL PROTECTED] tmp]$ ls -l /dev/st0* crw-rw---- 1 root disk 9, 0 Aug 6 13:23 /dev/st0 crw-rw---- 1 root disk 9, 96 Aug 6 13:23 /dev/st0a crw-rw---- 1 root disk 9, 32 Aug 6 13:23 /dev/st0l crw-rw---- 1 root disk 9, 64 Aug 6 13:23 /dev/st0m I am a member of group disk and can therefore read and write. carl -- carl lowenstein marine physical lab u.c. san diego [EMAIL PROTECTED] -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
