* Dustin J. Mitchell <dustin AT zmanda DOT com> [20071220 14:30]:
> On Dec 20, 2007 1:52 PM, Jean-Francois Malouin
> <Jean-Francois.Malouin AT bic.mni.mcgill DOT ca> wrote:
> > I've attached the relevent sendbackup debug file but nothing
> > looks suspicious in it, at least to me.
> > Both client and server are Debian/etch 64bit systems running
> > 2.6.21.5-i686-64-smp and 2.6.22.2-i686-64-smp respectively.
> 
> So this is operating with DLE /export_raid12/bicadmin1/amanda-rsync.
> Which of those is the directory that should be automounted, and which
> one had the 'r' inserted?

That's what is puzzling! Why on Earth is automount trying
/data/rbohbot or /data/bohbot/rbohbot1 when this DLE
/export_raid12/bicadmin1/amanda-rsync is under amanda eye's...

/data/bohbot/bohbot1 is in the automount maps on this amanda client:
/export_raid00/data-bohbot-bohbot1 mounts as /data/bohbot/bohbot1 as
on all the other NFS clients but it has nothing to do with the DLE
/export_raid12/bicadmin1/amanda-rsync! /export_raid00 and
/export_raid12 are two local raid partitions on the client: apart from
that they are totally unrelated.

> Can you duplicate the error by triggering an automount via e.g., "ls"?

No. I even rerun the tar command from the sendbackup debug file 
to double check and automount didn't trigger:

/bin/tar --create --file /dev/null --directory \
/export_raid12/bicadmin1/amanda-rsync --one-file-system \
--listed-incremental /tmp/amanda-rsync_0.new --sparse \
--ignore-failed-read --totals .
Total bytes written: 7268710400 (6.8GiB, 3.3GiB/s)

This is turning a little bit like a goose chase at the moment and I'm
sure you have more important things on your plate. I'll continue to
investigate this (minor) issue on my side and if ever something comes
up I'll post it.

thanks for you time and patience,
jf

> 
> Dustin
> 
> -- 
> Storage Software Engineer
> http://www.zmanda.com

-- 
<° ><