burning big files to DVD
Up to around 500Mb our DVD burner works fine. Beyond that, K3B finishes without errors but the DVD only contains the first part of the archive. We are trying to backup around 3.3GB consisting of a single tar file of our lan /home directory. There are no clues in /var/log. We have tried DVD-R and DVD-RW of various different makes. We first tar it to disk and then attempt to burn it. The disk tarball unpacks correctly. Any ideas on where to start? Thanks, Steve.
Steve Kratz wrote:
Any ideas on where to start? Thanks, Steve.
Non-expert thoughts-- Where is your "temp" image being stored, and is there enough free space on that device?
(Might be sending you in a completely wrong direction, but who knows :)
I usually back up my data on DVD using K3b and I have never encountered troubles, but I do not create images on the hard disk, but I directly write data on DVD. Try to do the same: I think Steve Kratz hint could be the right one. LM ................................................................................ Luca Mollica Dulbecco Telethon Institute (Biomolecular NMR Lab) DIBIT-HSR,Via Olgettina 58, 1B4 20132 Milano (Italy) Tel: 0039-02-26434824(Office)/26433497(Lab) Fax: 0039-02-26434153 E-mail: mollica.luca@hsr.it There is something to be learned from a rainstorm. When meeting with a sudden shower, you try not to get wet and quickly run along the road. But doing such things as passing under the eaves of houses, you still get wet. When you are resolved from the beginning, you will not be perplexed though you will still get the same soaking. This understanding extends to everything. -Hagakure- ................................................................................
Op vrijdag 15 oktober 2004 17:04, schreef steve-ss:
We are trying to backup around 3.3GB consisting of a single tar file of our lan /home directory. There are no clues in /var/log. We have tried DVD-R and DVD-RW of various different makes. We first tar it to disk and then attempt to burn it. The disk tarball unpacks correctly.
Any ideas on where to start?
There is a filesystem limit at around 2GB. Perhaps you run into such a problem... -- Richard Bos Without a home the journey is endless
On Friday 15 October 2004 14:43, Richard Bos wrote:
Op vrijdag 15 oktober 2004 17:04, schreef steve-ss:
We are trying to backup around 3.3GB consisting of a single tar file of our lan /home directory. There are no clues in /var/log. We have tried DVD-R and DVD-RW of various different makes. We first tar it to disk and then attempt to burn it. The disk tarball unpacks correctly.
Any ideas on where to start?
There is a filesystem limit at around 2GB. Perhaps you run into such a problem...
Take a look at Daromizer which works with DAR, a backup tool provided with SuSE. Just 6 days ago I ran Daromizer which does the following: 1) Starts DAR to build a 4.7GB tar file (as I specified) 2) Waits for the first file to be complete (and DAR continues to build the next file) 3) Burns the first file to a DVD (in my case... works for CD's too) 4) Waits for the next file to complete...... etc. Written by Michael Cocke who is a member of this list, it seems to be doing everything that you want to do. But at the very least, you can look at the code and see what techniques are in use. Daromizer can be found at: http://www.catherders.com/software.html
On Friday 15 October 2004 21:19, Bruce Marshall wrote:
On Friday 15 October 2004 14:43, Richard Bos wrote:
Op vrijdag 15 oktober 2004 17:04, schreef steve-ss:
We are trying to backup around 3.3GB consisting of a single tar file of our lan /home directory. There are no clues in /var/log. We have tried DVD-R and DVD-RW of various different makes. We first tar it to disk and then attempt to burn it. The disk tarball unpacks correctly.
Any ideas on where to start?
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?
Steve, On Friday 15 October 2004 13:43, steve-ss wrote:
On Friday 15 October 2004 21:19, Bruce Marshall 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.
Check out the topic thread "NFS versus Samba" from this list last month.
Here's the most pertinent post from Martin Farmilo (
Yes - the issue isn't Samba (the server), but smbfs (the client). And as Steve has pointed out, you can override the default to allow > 2gb files. But you can also use cifs instead, which doesn't have the limit. You just specify cifs in the mount command, instead of smbfs.
Randall Schulz
On Friday, 15 October 2004 23.04, Randall R Schulz wrote:
Steve,
On Friday 15 October 2004 13:43, steve-ss wrote:
On Friday 15 October 2004 21:19, Bruce Marshall 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?
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. 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.
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.
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.
Checked K3B but can't find the UDF bit. Question: If it were a hardware fault, would we see something to that effect in /var/log/messages? Also our burner is hdc, the master on the second ide drive. Still no success.
On Friday 15 October 2004 21:19, Bruce Marshall wrote:
On Friday 15 October 2004 14:43, Richard Bos wrote:
Op vrijdag 15 oktober 2004 17:04, schreef steve-ss:
We are trying to backup around 3.3GB consisting of a single tar file of our lan /home directory. There are no clues in /var/log. We have tried DVD-R and DVD-RW of various different makes. We first tar it to disk and then attempt to burn it. The disk tarball unpacks correctly.
Any ideas on where to start?
There is a filesystem limit at around 2GB. Perhaps you run into such a problem...
Take a look at Daromizer which works with DAR, a backup tool provided with SuSE.
Just 6 days ago I ran Daromizer which does the following:
1) Starts DAR to build a 4.7GB tar file (as I specified) 2) Waits for the first file to be complete (and DAR continues to build the next file) 3) Burns the first file to a DVD (in my case... works for CD's too) 4) Waits for the next file to complete...... etc.
Yep. Looks like just the thing. But still a bit confused: So is it splitting the 4.7GB file into smaller files first? Because you can't have a 4.7GB file because it's too big? What does 'filesystem limit' mean? Is that the size of the biggest file I can make? Or does it refer to the size of a file that K3B can handle?
participants (7)
-
Anders Johansson
-
Bruce Marshall
-
Luca Mollica
-
Randall R Schulz
-
Richard Bos
-
Steve Kratz
-
steve-ss