Steve,
Ever since my latest update from Red Hat, my VXA-2 tape library
has stopped working. It appears /dev/tape is now a directory
instead of a link to /dev/nst0 and every command I give to the
drive returns /dev/nst0: Input/output error.
See the following Red Hat bug:
On 04.08.2008 13:45, Chris Hoogendyk wrote (please find the answer below the
original text):
Steven Backus wrote:
Ever since my latest update from Red Hat, my VXA-2 tape library
has stopped working. It appears /dev/tape is now a directory
instead of a link to /dev/nst0 and every command I
I was doing some amanda testing and labeled a tape. Afterwards I backed up to
the tape using tar not amanda. I used the following syntax tar -c -b 4096 -f
/dev/nst0 /mnt/mail/logancty. I am unable to even list the files on the tape
using tar -t /dev/nst0. We have found that we are able to
Matthew Marlowe [EMAIL PROTECTED] writes:
See the following Red Hat bug:
https://bugzilla.redhat.com/show_bug.cgi?id=289381
This bug says:
mt status attempts to use /dev/tape, as a device, when it's a
directory
This could be it, does amanda use this for tape commands?
Are you using
Dustin writes:
Amanda uses what was supplied in the TAPEDEV parameter directly.
Then someone busted more than just the mt status command:
amtape genepi current
returns:
amtape: scanning current slot in tape-changer rack:
slot 2: not an amanda tape (Input/output error)
because it was an
On Tue, Aug 5, 2008 at 11:09 AM, Steven Backus
[EMAIL PROTECTED] wrote:
This could be it, does amanda use this for tape commands?
Amanda uses what was supplied in the TAPEDEV parameter directly.
Dustin
--
Storage Software Engineer
http://www.zmanda.com
On Fri, Aug 1, 2008 at 2:50 PM, Gene Heskett [EMAIL PROTECTED] wrote:
Running it every night Dustin the only wart is the reported compression in
the emailed report, that is generally completely bogus. I have posted about
it, but no one replied AFAIK.
OK, my apologies for not getting back to
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
On Tue, Aug 5, 2008 at 3:45 PM, Gene Heskett [EMAIL PROTECTED] wrote:
When was that, Dustin? This has been a minor niggle to me since back in the
2.5.x days. Am I the only one that actually reads these email reports amanda
can send?
You're probably reading them more closely than others :)
On Tuesday 05 August 2008, Dustin J. Mitchell wrote:
On Tue, Aug 5, 2008 at 3:45 PM, Gene Heskett [EMAIL PROTECTED]
wrote:
When was that, Dustin? This has been a minor niggle to me since back in
the 2.5.x days. Am I the only one that actually reads these email reports
amanda can send?
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
--
Marc
11 matches
Mail list logo