NFS mount tar incremental problem

Hello all,

I've been having a problem with incremental dumps on a NFS mountedNetapp. AMANDA runs great until I reboot the client (or remount theNFS shares on the client). At that point, while calcsize predicts whatI believe is the correct incremental dump size, tar proceeds to do afull dump of all the NFS mounted files. I believe this has to due withsomething changing between mounts that tar is translating as a changeto all files. Upon reading some of the documentation for tar, itindicated that in the incremental dump gnutar-lists, there should be a"1" preceding every entry to indicate that the file is NFS mountedbecause (Quoting http://www.gnu.org/software/automake/manual/tar/Incremental-Dumps.html"):

"Metadata stored in snapshot files include device numbers, which,obviously is supposed to be a non-volatile value. However, it turnsout that NFS devices have undependable values when an automounter getsin the picture. This can lead to a great deal of spurious redumping inincremental dumps, so it is somewhat useless to compare two NFSdevices numbers over time. The solution implemented currently is toconsiders all NFS devices as being equal when it comes to comparingdirectories; this is fairly gross, but there does not seem to be abetter way to go."

Here is an example from one of my gnutar-lists, showing what I believeare preceding zeroes, indicating that tar thinks that the files arenot on NFS:

1201070794^@37216648^@0^@947801240^@0^@24^@8623377^@./unclaimed_afs/nmlhome/mcbride/.desktop-nauset.dartmouth.edu/0.0^@Y4Dwmdeskname^@Y4Dwmdesks^@Y4Dwmdesks.bak^@Y4Dwmsession^@^@^@0^@1180594753^@523384000^@24^@9457059^@./spacescience/web/wl/per/HenrysForkFishing^@YIMG_0103.jpg^@YIMG_0104.jpg^@YIMG_0105.jpg^@YIMG_0106.jpg^@YIMG_0107.jpg^@YIMG_0108.jpg^@YIMG_0109.jpg^@YIMG_0110.jpg^@YIMG_0111.jpg^@YIMG_0112.jpg^@YIMG_0113.jpg^@YIMG_0114.jpg^@YIMG_0115.jpg^@YIMG_0116.jpg^@YIMG_0117.jpg^@YIMG_0118.jpg^@YIMG_0119.jpg^@YIMG_0120.jpg^@YIMG_0121.jpg^@YIMG_0214.jpg^@^@^@0^@1170258810^@0^@24^@11505238^@./paulsen/MAC_Keith/Mac_NIH/Proposals/Breast PPG/Original Proposal '98/Letters^@


Here's how the FS is mounted in /etc/fstab:

192.168.0.2:/vol/research /mnt/thayerfs/research nfshard,rsize=32768,wsize=32768 0 0


And here is an example disk list entry:
tardis  /mnt/thayerfs/research_p-z /mnt/thayerfs/research {
  nocomp-test
  include "./[p-zP-Z]*"
}

Has anyone run into this problem, or know how to fix it?

My System:

Ubuntu 7.10 i386
Gnutar 1.18
AMANDA 2.5.2p1

Thank you :-)

Jordan