Search:

Type: Posts; User: martineau

Page 1 of 20 1 2 3 4

Search: Search took 0.02 seconds.

  1. What was the output? What was the exit status...

    What was the output?
    What was the exit status (echo $?)
    Try to run only the tar command as root
  2. Remove the first runtar argument...

    Remove the first runtar argument
    /usr/libexec/amanda/runtar hatteras /bin/tar --create --file /dev/null --numeric-owner --directory / --one-file-system --listed-incremental...
  3. All fixes are committed and will be in 3.4.4. ...

    All fixes are committed and will be in 3.4.4.

    Thanks for your help, you did a great job to identify the bug.
  4. I committed the fix to...

    I committed the fix to packaging/rpm/amanda.spec.src
  5. Try the attached patch! Don't forget to re-add...

    Try the attached patch!

    Don't forget to re-add the 'v' falg in the tar command

    g_ptr_array_add(argv_ptr, g_strdup("-xpGvf"));
  6. I think you find the problem. Can you do...

    I think you find the problem.

    Can you do another test to be sure?
    In recover-src/extract_list.c,change the line 2015 form

    g_ptr_array_add(argv_ptr, g_strdup("-xpGvf"));
    to
    ...
  7. There is one more thread in amfetchdump because...

    There is one more thread in amfetchdump because it do the decompression, which is done by amrecover in the amidxtaped case.

    Add the following line to amanda.conf


    debug-recovery 9

    The new...
  8. SInce you get a timeout, you must check in the...

    SInce you get a timeout, you must check in the amandad and sendsize debug file to find why they didn't reply
  9. everything looks good. In the amrecover console,...

    everything looks good.
    In the amrecover console, did it show that it read some data?
    Do you see something at the same in the system error log?
  10. You said you can restore it with amfetchdump, can...

    You said you can restore it with amfetchdump, can you restore it again and post the amfetchdump debug file.
    I would like to compare them.
  11. Try with: device-property "nb-threads-backup"...

    Try with:
    device-property "nb-threads-backup" "1"
    device-property "nb-threads-recovery" "1"
    device_property "VERBOSE" "YES"

    And post the complete amidxtaped debug files ( add a...
  12. Since you run amrecover on the server, can you...

    Since you run amrecover on the server, can you try with the 'local' auth?
    $ amrecover -oauth=local ...
  13. defunct process are correct, amanda do not wait...

    defunct process are correct, amanda do not wait for all its child processes.
    The gzip should be on the machine you are running amrecover
    Can you also get the stacktrace of amrecover? and that gzip?...
  14. client or server compressed? Which compression...

    client or server compressed?
    Which compression are you using?
    What the decompression program is doing? Get a stack trace of it.

    The data go from amidxtaped -> decompression -> amandad ->...
  15. It is hang in a write. This write is to either a...

    It is hang in a write.
    This write is to either a software decryption/decompression program, do your data is compressed or encrypted?
    or it is a write to the amandad process.
  16. Can you attach gdb to the running amidxtaped and...

    Can you attach gdb to the running amidxtaped and get the stack trace of all threads?

    $ gdb -p 'pid of amidxtaped'
    (gdb) thread apply all bt
    ...
    (gdb) quit
  17. Which auth are you using? is it correctly...

    Which auth are you using? is it correctly configured?
    Do 'amcheck -c' succeed, you should not try amdump until amcheck succeed.
    Post all relevant debug files.
  18. Replies
    2
    Views
    114

    The slot is probably irrelevant. Are you using a...

    The slot is probably irrelevant.
    Are you using a holding disk?
    Increase the blocksize.
  19. GNUTAR require a mount point, md1 is not a mount...

    GNUTAR require a mount point, md1 is not a mount point, use the mount point '/'.
  20. Replies
    0
    Views
    146

    Sticky: Amanda 3.4.3 Released

    Hello,

    The Amanda core team is pleased to announce the release of Amanda 3.4.3.
    There is a major issue in 3.4, 3.4.1 and 3.4.2, all users should upgrade to 3.4.3 as soon as possible.
    This is a...
  21. Replies
    1
    Views
    592

    Sticky: Amanda 3.4.2 Released

    Hello,

    The Amanda core team is pleased to announce the release of Amanda 3.4.2.
    This is a bugfix release for Amanda-3.4.1.

    Source tarballs are available from


    http://www.amanda.org
    ...
  22. Replies
    2
    Views
    358

    From your post, it is not clear which process...

    From your post, it is not clear which process remove the file.

    amrecover warn you about the fact that files can be removed.

    It might be a difference in the way gnutar works.

    Do the extract...
  23. It should be rewritten as: STORAGE_API ...

    It should be rewritten as:


    STORAGE_API
    The default is AWS4 if S3-HOST is set in the configuration file and end with '.amazonaws.com', otherwise it is S3.
  24. The problem is because of the / character in the...

    The problem is because of the / character in the prefix

    tpchanger "chg-multi:s3:myrar-backup/test_backup/slot-{01,02,03,04,05,06,07,08,09,10}"

    The / between test_backup and slot...

    The...
  25. Try to emove the ":443" in the s3-host...

    Try to emove the ":443" in the s3-host device_property.
Results 1 to 25 of 500
Page 1 of 20 1 2 3 4