I have an Ultrium LTO-4, and cannot get it to work with Amanda.
[EMAIL PROTECTED] ~]$ amlabel WeeklySet1 Weekly-01
Reading label...
Can't open tape device /dev/nst0: Bad file descriptor
amlabel: Could not open device tape:/dev/nst0.
Here is pertinent section of my /etc/amanda/Weekl
Vectorz Sigma schrieb:
[EMAIL PROTECTED] ~]$ amlabel WeeklySet1 Weekly-01
Reading label...
Can't open tape device /dev/nst0: Bad file descriptor
amlabel: Could not open device tape:/dev/nst0.
Allready tried if the drive is accessable by mt directly?
# mt -f /dev/nst0 status
--
On Tue, Aug 5, 2008 at 3:04 PM, Vectorz Sigma <[EMAIL PROTECTED]> wrote:
> I have an Ultrium LTO-4, and cannot get it to work with Amanda.
You had pasted some other diagnostic output that I didn't recognize to
#amanda. Can you give some more details? Also, please have a look in
your kernel logs t
My tapedev entry that works is tapedev "/dev/nst0" not tapedev "tape:/dev/nst0"
I have used the follow tape specific entries in my amanda.conf:
tapedev "/dev/nst0" # Linux @ tuck, important: norewinding
tapetype LTO4 # what kind of tape it is (see tapetypes below)
labelstr "^FULLBACK-[0-9][0-9]
tape:/dev/nst0" instead.
Can't open tape device /dev/nst0: Bad file descriptor
amlabel: Could not open device /dev/nst0.
On Wed, Aug 6, 2008 at 7:22 AM, Doyle Collings <[EMAIL PROTECTED]>wrote:
> My tapedev entry that works is tapedev "/dev/nst0" not tapedev
> &qu
Marc -- Yes, I have tried to access it directly with tar, also mt commands
to rewind, etc. Also note that initially I setup Bacula on this system and
that worked so I know the drive is legit on that device name. I decided not
to use Bacula because the maintenance of the MySQL db got really out o
that writes the
deprecation warning adds the prefix, and things go merriliy on. So
the error is, in particular:
> Can't open tape device /dev/nst0: Bad file descriptor
> amlabel: Could not open device /dev/nst0.
Which basically amounts to: "the kernel said there was an error." S
I would also verify that nst0 is assigned to your LTO 4 drive
What brand of Ultrium LTO 4 do you use. Mine is a Tandberg Data or Exabyte. I
use the ltoTool to check and see if the device is being recognized. If your
Ultrium LTO 4 is not an Tandberg, I am sure the manufacturer has a tool to
ve
The mystery deepens.
Can you run 'amlabel' under strace or truss or your local equivalent?
I'd like to know what syscall is returning EBADFD (Bad file
descriptor). Also, please remind me what version of Amanda you're
running.
You can send the strace output to me privately for analysis if you'd
l
TIA for your help thus far. Following your advice, here is a diag tool I
ran on my HP Ultrium LTO-4 that indicates all is working well on it and
verifies it is /dev/nst0. I have checked my logs and the last error I've
seen was a few days ago, nothing produced by the diags done recently.
Main >
I downgraded to Amanda 2.5.2p1 and it gave me a better clue when running
amlabel. Basically it said /dev/nst0 = permission denied. I've been
running the amlabel command as amandabackup but didn't realize you need to
give permissions to the /dev/nst0 device (which was 750 perms and owned by
root:r
On Wed, Aug 6, 2008 at 7:32 PM, Vectorz Sigma <[EMAIL PROTECTED]> wrote:
> I downgraded to Amanda 2.5.2p1 and it gave me a better clue when running
> amlabel. Basically it said /dev/nst0 = permission denied. I've been
> running the amlabel command as amandabackup but didn't realize you need to
>
12 matches
Mail list logo
