Amanda-Users

NFS strangeness

2006-09-08 17:15:29
Subject: NFS strangeness
From: Steffan Vigano <svigano AT boothcreek DOT com>
To: amanda-users AT amanda DOT org
Date: Fri, 08 Sep 2006 14:08:59 -0700
Hello all,

Just wondering if anyone might be able to shed some light on my problem... we recently got a SnapServer on our network and would like to use our existing Amanda install to back it up via NFS but so far have been unsuccessful.

- FreeBSD 4.7-RELEASE
- Amanda v2.4.4b1
- GNU tar v1.13.25

I have tried mounting the NFS shares onto the main Amanda backup host as well as other servers being backed up via Amanda. I can manually, from the command line, read/write and tar up the attached NFS shares without issue, both as root and user Amanda. Yet when Amanda runs through it's backup process, nothing gets backed up from that share. I've checked the logs, and there are no errors showing. Running an amrecover shows the root directory that the share is mounted on, but there are no files or directories within to recover. I've tried changing the dump type in amanda.conf to both DUMP and GNUTAR for the partition in question. No change. I've also tried an NFS mount from an alternate FreeBSD machine to rule out the SnapServer. Same issue.

Here are the runtar and sendsize debug files:

runtar: debug 1 pid 49585 ruid 1002 euid 0: start at Fri Sep 8 13:41:26 2006
gtar: version 2.4.4b1
running: /usr/bin/tar: gtar --create --file - --directory /nfs --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/phatb.boothcreek.net_dev_aacd0s2h_1.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendbackup._dev_aacd0s2h.20060908134126.exclude .

sendsize: debug 1 pid 50252 ruid 1002 euid 1002: start at Fri Sep 8 13:59:38 2006
sendsize: version 2.4.4b1
sendsize[50252]: time 0.005: waiting for any estimate child
sendsize[50257]: time 0.005: calculating for amname '/dev/aacd0s2h', dirname '/nfs', spindle -1 sendsize[50257]: time 0.006: getting size via gnutar for /dev/aacd0s2h level 0 sendsize[50257]: time 0.008: spawning /usr/local/libexec/runtar in pipeline sendsize[50257]: argument list: /usr/bin/tar --create --file /dev/null --directory /nfs --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/phatb.boothcreek.net_dev_aacd0s2h_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._dev_aacd0s2h.20060908135938.exclude .
sendsize[50257]: time 0.052: Total bytes written: 102400 (100kB, 3.1MB/s)
sendsize[50257]: time 0.053: .....
sendsize[50257]: estimate time for /dev/aacd0s2h level 0: 0.045
sendsize[50257]: estimate size for /dev/aacd0s2h level 0: 100 KB
sendsize[50257]: time 0.053: waiting for /usr/bin/tar "/dev/aacd0s2h" child
sendsize[50257]: time 0.053: after /usr/bin/tar "/dev/aacd0s2h" wait
sendsize[50257]: time 0.054: done with amname '/dev/aacd0s2h', dirname '/nfs', spindle -1
sendsize[50252]: time 0.054: child 50257 terminated normally
sendsize: time 0.054: pid 50252 finish time Fri Sep  8 13:59:38 2006

as you can see... it only sees the 100k of real test files that I have in the /nfs directory, and not the actual mounts that live under /nfs. ???

Am I missing something easy? Anything special I need to add to 'amanda.conf'? or 'disklist'? I do just mount the NFS share to an existing entry in my disklist, right? Rather then adding the NFS mount as a separate entry? I've check all the permissions on the share (no_root_squash, etc)... I'm at a loss. Digging around the net, I've been unable to find any clear docs on what the proper setup might need to look like. Anyone have any more suggestions about next steps?

Thanks a bunch,
-Steffan

<Prev in Thread] Current Thread [Next in Thread>