* Dustin J. Mitchell <[EMAIL PROTECTED]> [20071220 13:05]:
> On Dec 20, 2007 11:39 AM, Jean-Francois Malouin
> <[EMAIL PROTECTED]> wrote:
> > Dec 20 10:14:24 grumio automount[7198]: failed to mount /data/rbohbot
> > Dec 20 10:14:24 grumio automount[7199]: failed to mount
> > /data/bohbot/rbohbot1
> > ...
> > about 10 of them.
> >
> > On the client runtar was spawn at 10:14:24
> >
> > ~# cat /tmp/amanda-av/client/right2/runtar.20071220101424.debug
> > runtar: debug 1 pid 7218 ruid 666 euid 0: start at Thu Dec 20 10:14:24 2007
> > runtar: time 0.000: version 2.5.2p1
> > /bin/tar version: tar (GNU tar) 1.14
> >
> > config: right2
> > runtar: debug 1 pid 7218 ruid 0 euid 0: rename at Thu Dec 20 10:14:24 2007
> > running: /bin/tar: 'gtar' '--create' '--file' '-' '--directory'
> > '/export_raid12/bicadmin1/amanda-rsync' '--one-file-system'
> > '--listed-incremental'
> > '/opt/amanda/var/amanda/right2/gnutar-lists/grumio_export_raid12_bicadmin1_amanda-rsync_0.new'
> > '--sparse' '--ignore-failed-read' '--totals' '.'
> > runtar: time 0.061: pid 7218 finish time Thu Dec 20 10:14:24 2007
>
> This 'runtar' invocation is for a different DLE --
> /export_raid12/bicadmin1/amanda-rsync. It's possible this is an error
> in amanda or tar, but I would need to see a rundump, sendbackup, or
> sendsize log that either includes the 'r', or includes the DLE without
> the 'r' (in which case we can look to a bug in tar). While I'm asking
> for info -- what systems are these?
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.
> My suspicion remains with the automounter, and that it is for some
> reason falling back to the 'r'-bearing fiename when the normal mount
> fails. If Amanda or tar were doing this, then it would not be
> sporadic.
It happens on all the clients all the time and it's not sporadic at
all. I've also seen the same behaviour on a irix server/client.
Gnutar is 1.14 on Debian and 1.13.25 on irix.
Looking further in the syslogs I can correlate 100% between the
automount failures and either sendbackup or sendsize starting.
strange. jf
>
> Dustin
>
> --
> Storage Software Engineer
> http://www.zmanda.com
--
<° ><
sendbackup: debug 1 pid 7189 ruid 666 euid 666: start at Thu Dec 20 10:14:24
2007
sendbackup: version 2.5.2p1
Could not open conf file "/opt/amanda/etc/amanda/amanda-client.conf": No such
file or directory
Reading conf file "/opt/amanda/etc/amanda/right2/amanda-client.conf".
sendbackup: debug 1 pid 7189 ruid 666 euid 666: rename at Thu Dec 20 10:14:24
2007
sendbackup req: <GNUTAR /export_raid12/bicadmin1/amanda-rsync 0
1970:1:1:0:0:0 OPTIONS |;auth=bsdtcp;no-record;>
parsed request as: program `GNUTAR'
disk `/export_raid12/bicadmin1/amanda-rsync'
device `/export_raid12/bicadmin1/amanda-rsync'
level 0
since 1970:1:1:0:0:0
options `|;auth=bsdtcp;no-record;'
sendbackup: start: grumio:/export_raid12/bicadmin1/amanda-rsync lev 0
sendbackup-gnutar: time 0.041: doing level 0 dump as listed-incremental to
'/opt/amanda/var/amanda/right2/gnutar-lists/grumio_export_raid12_bicadmin1_amanda-rsync_0.new'
sendbackup-gnutar: time 0.414: doing level 0 dump from date: 1970-01-01
0:00:00 GMT
sendbackup: time 0.416: spawning /opt/amanda/libexec/runtar in pipeline
sendbackup: time 0.416: argument list: runtar right2 gtar --create --file -
--directory /export_raid12/bicadmin1/amanda-rsync --one-file-system
--listed-incremental
/opt/amanda/var/amanda/right2/gnutar-lists/grumio_export_raid12_bicadmin1_amanda-rsync_0.new
--sparse --ignore-failed-read --totals .
sendbackup-gnutar: time 0.417: /opt/amanda/libexec/runtar: pid 7218
sendbackup: time 0.417: started backup
sendbackup: time 337.150: 47: size(|): Total bytes written: 7268710400
(6.8GiB, 21MiB/s)
sendbackup: time 337.157: parsed backup messages
sendbackup: time 337.157: pid 7189 finish time Thu Dec 20 10:20:01 2007
