This all sounds great. Not to sound like an overworked developer, but
could you all please update the FAQ entry accordingly? ;)
http://wiki.zmanda.com/index.php/FAQ:Why_can_I_write_new_labels_to_my_tapes_but_can%27t_read_the_old_ones%3F
Dustin
--
Storage Software Engineer
http://www.zmanda.
For example, in your rc.conf
file you may have:
/bin/mt -f /dev/nst0 defcompression 0
/bin/mt -f /dev/nst0 defblksize 0
I think this probably gets too specific.
The error could just as easily occur because amanda is upgraded to new
binaries which are not compiled for the proper blocksize at
Dustin J. Mitchell" <[EMAIL PROTECTED]> writes:
> Are there more details to add? The 'mt' invocations in rc.conf may be
> helpful to others, for example.
FAQ:Why can I write new labels to my tapes but can't read the old ones?
Check your blocksize. This behavior occurs when the tape unit is
set
"Dustin J. Mitchell" <[EMAIL PROTECTED]> writes:
> I haven't followed this too closely, but are there some takeaway
> messages that could be worked into a FAQ here?
> http://wiki.zmanda.com/index.php/FAQ
FAQ:Why can I write new labels to my tapes but can't read the old ones?
Check your blocksi
On Thu, Aug 7, 2008 at 5:25 PM, Steven Backus
<[EMAIL PROTECTED]> wrote:
> FAQ:Why can I write new labels to my tapes but can't read the old ones?
>
> Check your blocksize. This behavior occurs when the tape unit is
> set to have a particular block size (that may not match at read
> time what was
On Thu, Aug 7, 2008 at 1:06 PM, Steven Backus
<[EMAIL PROTECTED]> wrote:
> Thanks to John Hein and everyone.
I haven't followed this too closely, but are there some takeaway
messages that could be worked into a FAQ here?
http://wiki.zmanda.com/index.php/FAQ
Dustin
--
Storage Software Engineer
<[EMAIL PROTECTED]> writes:
> I've seen problematic behavior when the tape unit is set to have a
> particular block size (that may not match at read time what was used
> to write a tape).
That was the problem. In my rc.local file I have:
/bin/mt defcompression 0
/bin/mt defblksize 0
But with th
Steven Backus wrote at 10:20 -0600 on Aug 7, 2008:
> I've determined my drive can label tapes but can't read old
> tapes. I get the Input/Output error whenever trying to read a
> previously labeled tape or dd out anything. However, if I re-label
> the tape it works again. Does this indica
I've determined my drive can label tapes but can't read old
tapes. I get the Input/Output error whenever trying to read a
previously labeled tape or dd out anything. However, if I re-label
the tape it works again. Does this indicate a failing drive? Any
other ideas?
Thanks,
Steve
--
Steve
Matthew Marlowe <[EMAIL PROTECTED]> wrote:
> Are you using RHEL or Fedora? The bug is reported for fedora 8 but
> we just noticed a similar issue on a RHEL5.2 box (perhaps this is
> one of the feature updates carried over from fedora during the 5.2
> upgrade).
I'm on RHEL 4.x, latest updates, t
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
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 amand
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
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
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:
https://bugzilla.
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 give to the
drive returns /dev/nst0: Input/output error. I've tried removing
/dev/tape and lin
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. I've tried removing
/dev/tape and linking it to /dev/nst0 with
17 matches
Mail list logo
