Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15

Thread: No more maxtapeblocksize, what now?

  1. #11
    Join Date
    Mar 2007
    Location
    Chicago, IL
    Posts
    688

    Default

    Moving to amanda-hackers sounds *great*. I detest forums!

    Code:
    4276:   read(4, 0x0004C900, 32768)                      Err#5 EIO
    What the heck? It *is* using the wrong block size.

    Let's pick this up on the mailing list..

  2. #12
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    Can you try the following command:
    amcheckdump <config> -t 20090414
    amfetchdump <config> .\* /\* 20090414

  3. #13

    Default

    Quote Originally Posted by martineau View Post
    Can you try the following command:
    amcheckdump <config> -t 20090414
    amfetchdump <config> .\* /\* 20090414
    We've moved this thread to the amanda-hackers mailing list. I've responded to your query there.

  4. #14

    Default

    Quote Originally Posted by darin View Post
    This is the tail end of the truss output from 'truss -f -o ./truss.out amrestore -b 512 tape:/dev/rmt/0cn'
    Did you mean to use -b 524288 ? When I pass amrestore on Solaris 10 anything less than 32768 it does a 32k read.

  5. #15

    Default

    It was a bug that has been addressed.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •