Thanks for the quick reply!
"John R. Jackson" wrote:
> What version of tar are you using?
1.13.17, which I understand is acceptable, correct?
> What kind of connection exists between client and server? Any firewalls
> or that kind of thing?
Should have been more clear here - svhsfiles is the tapehost as well, so
no networking issues - and other partitions on the box are backing up
correctly.
> What OS and version is the client? The server?
RedHat 6.0 - I did not apply any patches when building 2.4.2, as my
impression was that they were rolled in already (surmised from the
patches page only listing 2.4.1p1 patches). I had used the patches with
2.4.1 previously.
> What happens if you run the tar command listed in sendbackup*debug
> but replace the listed-incremental filename with an empty file (e.g.
> cp /dev/null to /tmp/empty and use that) and send stdout to /dev/null?
[root@svhsfiles /root]# su amanda -c "/usr/local/libexec/runtar \
--create --directory /home --listed-incremental /tmp/empty \
--sparse --one-file-system --ignore-failed-read --totals --file \
- /usr/local/lib/amanda/exclude.gtar --exclude-from \
/usr/local/lib/amanda/exclude.gtar > /dev/null"
bash: /root/.bashrc: Permission denied
/usr/local/libexec/runtar: Removing leading `/' from member names
Total bytes written: 10240 (10kB, ?B/s)
[root@svhsfiles /root]# cat /tmp/empty
981646673
[root@svhsfiles /root]#
> Is there any chance you can catch it in this state and run a truss on
> the sendbackup to see what it is doing? And maybe attach a debugger
> to sendbackup and GNU tar to find out where they are ("where" to get a
> stack traceback)?
If you'll provide instructions on how to do this, I'd be happy to :)
--
Chris Hobbs Silver Valley Unified School District
Head geek: Technology Services Coordinator
webmaster: http://www.silvervalley.k12.ca.us/chobbs/
postmaster: [EMAIL PROTECTED]
