On 2006-04-04 11:48, David Leangen wrote:

[root@shinsaibashi amanda]# /bin/gtar --create --file /dev/null
--directory /usr/local/repo  --one-file-system
--listed-incremental /dev/null --sparse  --ignore-failed-read --totals .
/bin/gtar: ./xxx/db/__db.003: Warning: Cannot seek to 0: Bad file
descriptor
/bin/gtar: ./xxx/db/__db.004: Warning: Cannot seek to 0: Bad file
descriptor
/bin/gtar: ./xxx/db/__db.001: Warning: Cannot seek to 0: Bad file
descriptor

Having a closer look at my own installation, I see that I have
the same warning.  It has indeed to do with the combination of
sparse file handling and output in /dev/null.
Moreover, with --ignore-failed-read, the exit status is 0, all OK.
I still believe that is a bug in gnutar, but not critical.

When doing the backup itself (sendbackup, not sendsize) the output
is not to /dev/null, and the warning goes away too.

See also: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154882


So this is not the cause of your trouble.
What exactly is the error message that you get for those clients?


--
Paul Bijnens, xplanation Technology Services        Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************