On Wed, 21 Mar 2001, John R. Jackson wrote:
> OK. The first thing to do is look at the actual index files and see
> if they have the entries (this is sounding familiar, so if we've gone
> down this path before and I've forgotten, my apologies). If the files
> are listed, it's an amrecover problem.
To rewind the conversation -- gnutar 1.13.19 has been installed and it
fixes my solaris backup problem. The only remaining issue is the smb
clients.
> Once we know which of these is the area responsible, debugging it can
> proceed from there.
Looking at the index, the files are not listed.
Looking at a dump of all the files on the tape (dd style through tar), the
missing files were _not_ backed up. Thus amrecover is good, but somehow
things didn't get backed up.
But I think I've found the problem. The last file in the index is an 11GB
file. The backup server, if you recall, is Linux without the large
filesystem patches. My guess is that it all just died when it tried to get
through 11GB. A quick browse through the samba mailinglist says that large
filesystem support (lfs) isn't enabled by default in the latest 2.0.7
release for ostype "linux", even if you have the 2.4 kernel or the 2.2
patches. Anyone else run into this problem?
--
http://www.mchang.org/
http://decss.zoy.org/
