GithubHelp home page GithubHelp logo

Short write on tape device about amanda HOT 5 OPEN

cscottpnw avatar cscottpnw commented on August 15, 2024
Short write on tape device

from amanda.

Comments (5)

exuvo avatar exuvo commented on August 15, 2024

The setting you want to modify is tapetype { blocksize setting as it defaults to 32KB.
Try setting it lower maybe? I use 1MB on my LTO5 but LTO2 is tiny in comparison.

define tapetype LTO2 {
  blocksize 24 kbytes
}

from amanda.

cscottpnw avatar cscottpnw commented on August 15, 2024

I've tried a few different blocksize settings. None had an impact. The config I provided above just happened to not contain a blocksize.

Despite the history, I just tried a blocksize of 64 kybtes. Same problem

define tapetype LTO2-200 {
     comment "LTO Ultrium2 200/400"
     length 400000 mbytes
     blocksize 64 kbytes
     speed 20570 kps
}

Error:

FAILURE DUMP SUMMARY:
  hostname / lev 0  partial taper: Error writing block: Short write on tape device: Tried 65536, got 9216.  Is the drive using a block size smaller than 65536 bytes?

Thanks anyway,.

from amanda.

calhariz avatar calhariz commented on August 15, 2024

Could it be you have a problem with the hardware or BSD? Have you tried to write using tar to the tape device?

from amanda.

exuvo avatar exuvo commented on August 15, 2024

Oh yeah if you haven't tested manually: position the drive with mt, write some data to it (ex tar or dd, does not need to be a tape aware program for less than full tape writes), rewind with mt, read and verify the written data.

from amanda.

cscottpnw avatar cscottpnw commented on August 15, 2024

It could FBSD, but the issue still seems specific to AMANDA. Prior to opening this Issue, I successfully wrote/retrieved via dd, dump, gnutar, and bsdtar. The LTO drive was replaced, and produces the exact same error. I briefly considered the SCSI card, but there's zero evidence its having a problem. I've been successfully using tar as a mitigation measure since this issue began.

Nothing in the system reports problems. There's never anything relevant in dmesg, or any system logs. My current hunch is the OS is causing this. Same setup ran successfully on FBSD 12.x. This seems to start with FBSD 14.x. I haven't received response from the FBSD community. There doesn't seem to be many AMANDA users in that community. FWIW, I've been using AMANDA for over 25 years, and have never encountered a problem like this.

from amanda.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.