Re: tar escaping into a different file system

On Mon, Jul 31, 2006 at 09:52:10AM +0200, Geert Uytterhoeven wrote:
> 
> Finally I'm getting back on track after the tar 1.15.91-2 incremental changes.
> Due to this issue and my yearly holidays, my backups are long overdue and
> Amanda likes to do lots of level 0s (as expected).
> 
> I just noticed this in the mail log of last night's backup:
> 
> | /--  anakin / lev 0 FAILED [data write: Connection reset by peer]
> | sendbackup: start [anakin:/ level 0]
> | sendbackup: info BACKUP=/bin/tar
> | sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
> | sendbackup: info COMPRESS_SUFFIX=.gz
> | sendbackup: info end
> | ? gtar: ./proc/19106/fd/5: Warning: Cannot stat: No such file or directory
> | ? gtar: ./proc/19106/task/19106/fd/5: Warning: Cannot stat: No such file or
> | directory
> | ? gtar: ./proc/6490/task/19182: Warning: Cannot stat: No such file or
> | directory
> | ? gtar: ./proc/6490/task/19182/attr: Warning: Cannot stat: No such file or
> | directory
> | ? gtar: ./proc/6490/task/19182/attr: Warning: Cannot stat: No such file or
> | directory
> | ? gtar: ./proc/6490/task/19182/fd: Warning: Cannot stat: No such file or
> | directory
> | ? gtar: ./proc/6490/task/19182/fd: Warning: Cannot stat: No such file or
> | directory
> | ? gtar: ./proc/asound/card0/pcm0p/sub1: file changed as we read it
> | ? gtar: ./proc/irq/14/ide0: file changed as we read it
> | ? gtar: ./proc/sys/fs/mqueue: file changed as we read it
> | ? gtar: ./proc/sys/net/ipv6/conf/default: file changed as we read it
> | | gtar: ./dev/gpmctl: socket ignored
> | | gtar: ./dev/log: socket ignored
> | \--------
> 
> Since /proc is on a separate file system, tar is not supposed to enter that
> directory.
> 
> Anyone seen that before? I'm using tar 1.15.91-2 and amanda 1:2.5.0p2-1 (+ my
> backport of the fixes for tar 1.15.91, cfr.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378558), on Debian
> testing/unstable.
> 
> Is this another tar 1.15.91 breakage?
> 

Things to check might include:

Do the amanda debug files on the client show the tar argument list
with the "-l" or "--one-file-system" argument.

Do you have any "include" directives.  Tar will happily go to other
file systems if you specifically tell it to.  I once ran a DLE that
covered 3 or 4 tiny file systems in one DLE by using / as the 
starting directory and including /a, /b, /c, ... (the mount points).

If you run tar with the create and verbose (cv) options and the
output is to /dev/null (f /dev/null), then tar will output the
filenames of what it would backup, but doesn't.  It only visits
the inodes, not the datablocks.  So you could try 1.15.91 manually
and see if the output filenames include the /proc files.  Lots
of output, so probably collect to a file and search with less or more.
Also, don't forget the --one-file-system option.


-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)