Debian bug report logs - #1174
tar gives `Visible longname error'

Message received at debian-bugs:

From cus.cam.ac.uk!iwj10 Mon Jul 31 02:23:13 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0scr45-0005NPC; Mon, 31 Jul 95 02:23 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA14006
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 31 Jul 1995 02:23:10 -0700
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #36) id m0scr3x-000C0WC; Mon, 31 Jul 95 10:23 BST
Received: by chiark
	id <m0scOQf-0002ZaZ@chiark.al.cl.cam.ac.uk>
	(Debian /\oo/\ Smail3.1.29.1 #29.32); Sun, 30 Jul 95 03:48 BST
Message-Id: <m0scOQf-0002ZaZ@chiark.al.cl.cam.ac.uk>
Date: Sun, 30 Jul 95 03:48 BST
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: Debian bugs submission address <debian-bugs@pixar.com>
Subject: tar gives `Visible longname error'

Package: tar
Version: 1.11.8-1

My backup log reports:

tar --totals -lvvc -b32 -f/dev/st0 -T/var/local/backup/this-fsys >>log
tar: var: On a different filesystem; not dumped
tar: usr: On a different filesystem; not dumped
tar: u: On a different filesystem; not dumped
tar: old: On a different filesystem; not dumped
tar: cdrom: On a different filesystem; not dumped
tar: proc: On a different filesystem; not dumped
tar: dos: On a different filesystem; not dumped
tar: var/spool/news: On a different filesystem; not dumped
tar: u/ian: On a different filesystem; not dumped
tar: Visible longname error
Total bytes written: 1254490112

tar appears to write all the data, but exits with a non-zero exit
status.

The longest line in the 13Mb `log' file is
-rw-rw-r-- root/root            0 Feb 26 01:25 1995 usr/local/src/old/ncurses-1.8.7/runtime-tmp/usr/lib/terminfo/c/concept108-rv-4p link to usr/local/src/old/ncurses-1.8.7/runtime-tmp/usr/lib/terminfo/c/c108-rv-4p

(/var/local/backup/this-fsys contains:
TAPEID
etc/passwd
etc/group
.
usr
var
var/spool/news
u
u/ian
dos
old
TAPEID
)

I find this worrying.  Does it mean that the backup in question is not
useable ?  Perhaps I should go back to my old patched tar 1.11.2.

Ian.