On Friday, 15 October 2004 23.50, steve-ss wrote:
There is a filesystem limit at around 2GB. Perhaps you run into such a problem...
Does that mean that I can't have a file bigger than 2GB?
No, not if you do it right. I assume you're talking about SMB / Samba, not NFS, which has no such limit.
First of all, he said "the tar file unpacks correctly", so the file size on the disk can't possibly be the problem. Secondly, you really don't want to burn a file over a network connection, it's just too unreliable
The command used to burn the file might be the problem. Steve, what do you use? And do you see anything in /var/log/messages when you burn?
The burner is on a lan client which has the /home directory (the one we want to backup) fed to it by NFS. The tarball we make is stored on real hard disk (under /root) and it unpacks perfectly.
That's what I mean, the file you're burning should be on local disk. That you create it from a LAN share isn't important, but when you actually feed it to the burner it should come from a local disk
We use K3B to burn the tar file stored on disk to a DVD. K3B terminates correctly and there are no clues in /var/log/messages. The lan is 100% SuSE 9.1. No samba.
I'm not sure. Could it be that k3b for some reason thinks it's a CD it's burning and not a DVD? Go through the k3b settings you're using and make sure you have correct settings for a DVD, like UDF file system etc.