Are there file size limitations for DVDs with Fedora Core 5

[quinlan]

I am using the Nautilus CD/DVD Creator to burn archival .dat file extracted from 8mm tapes onto DVDs. As a test I extracted 4 .dat files from the tapes. The file sizes are as follows

62.7 mb
75.2 mb
166.6 mb
329.7 mb

The DVD burner is a Phillips DVD=/-RW DVD8801. The blank DVD has 4.7gb free.

I can burn a DVD with the first three files without error. When I try to burn a DVD with the fourth file, 329.7mb, Nautilus creates the image and then errors out

Error writing to disc. There was an error writing to disc.

I tried 2 other blank DVDs and received the same error.

I shutdown Fedora core 5 and restarted and tried to copy the previously successfully burnt three files with the DVD discs that created the error. The same error appeared -- Error writing to disc......

The DVD discs are brand new, so it is difficult to imagine that the DVD discs themselves are the issue.

Is there a file size limitation when using the Nautilus CD/DVD Creator ?

I'm installed k3b today to try burning the DVDs.
Thanks

[LocutusOfBorg]

The max size of a file that you can put on a iso filesystem is 2Gb: beyond that limit you need UDF filesystem. Your files are much smaller than this, so the problem lies somewhere else

[SlowJet]

I downloaded this 2.6 GB with firefox.

-rw-r--r-- 1 darwinhwebb darwinhwebb 2676559872 Oct 9 02:10 vista_5744.16384.061003-1945_x86fre_client-lrmcfre_en_dvd.iso

I also have several 3.3 GB iso called Fedora something, Redhat beta1, and Suse 9.3, Suse 10.1

The max fs size for ext3 is 8TB.
The max file size must be much bigger than 2 GB.

SJ

I think the opensuse 10.2 64-bit beta's dvds are over 4 GB.

[lazlow]

I think what was meant was the iso can be larger than 2gb but the largest file in the iso needs to be less than 2gb. If that is true, it would be an iso limitation and not a linux one.

I think you will be happier it you use K3b(you can use it on gnome or kde). When doing backups like this I found it more reliable to have k3b make an Iso(on the hard drive) and then burn it to media with verify on. When you form the iso on the fly, I think sometimes stuff gets goofy. The verify after burn option also is reassuring that what you sent was what was recieved.

Good Luck
Lazlow

[quinlan]

I tried to install k3b 11.24 by using the ./configure as suggested in INSTALL and received the following

checking build system type i686-pc-linux-gnu
checking host system type i686-pc-linus-gnu
checking target system type i686-pc-linux-gnu
checking for a BSD-compatiable install /usr/bin/install -c
checking for -p flag to install yes
checking whether build environment is sane yes
checking for gawk gawk
checking whether make sets $(MAKE) yes
checking for kde-config not found
configure errir the important program kde-config was not found. Please check whether you installed KDE correctly

I am a Solaris person and a Linux newbie. All I installed was Fedora Core 5

Please advise
Thanks

[quinlan]

Thanks for the info about DVD Disk limitations. Now that that is cleared up, it's obvious that DVD disk size isn't the issue. The files that we are trying to burn are proprietary files, but basically, one is a .dat file that has all the inquiries for the month and the other is a .dat file that has all the reports for the month. If I copy both an inquiry.dat and a report.dat file to Nautilus CD/DVD Creator, the DVD burns successfully. If I try to burn just the report.dat file alone, it fails with
error writing to disc
there was an error writing to disc

In /var/log/messages the error is
dyn1068542 kernal: cdrom : this disc doesn't have any tracks I recognise!

I found a reference to that error on Linux Forums
http://www.linuxforums.org/forum/red...tml#post380720
and did as advised, but no go.

Ok. Good. This means your USB device is getting detected. You do not need any special drivers. What you need is to mount this device manually, since it's apparently not getting mounted by Redhat automatically.


Code:
cd /mnt
mkdir usbdisk
mount -vfat /dev/sda usbdisk/
That *should* mount it for you. To unmount it, type this:


Code:
umount /mnt/usbdisk
You'll need to be root to create the usbdisk directory. If you already have a directory in /mnt for a usb device, just use that. There is a way to set this up in your /etc/fstab file so that you don't have to write so long a command every time, but I'm honestly too tired right now to go through the steps on that. Someone else can help you there.
__________________
Registered Linux user #270181
TechieMoe's Tech Rants
almost there

--------------------------------------------------------------------------------

works for both first command until last one execute this:

Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
Try this instead:


Code:
mount -t vfat /dev/sda /mnt/usbdisk__________________
Registered Linux user #270181
TechieMoe's Tech Rants

So after reading all that, I created usbdisk in /mnt and then issued the command
mount -t vfat /dev/dvd /mnt/usbdisk

The result was
mount -t vfat /dev/dvd /mnt/usbdisk
mount: block device /dev/dvd is write-protected mounting read-only
moutn: dev/dvd: can't read superblock

Any advice?
Thanks

[lazlow]

yum install k3b

It may be that the burner is recognizing .dat files as something special(like it does with .iso). Just to see try renaming it to .dat.x and burning it.

I have no idea where the stuff starting with "Ok.Good." comes from or what it is about. Please explain.

Lazlow

[quinlan]

The Ok good message came from http://www.linuxforums.org/forum/re...html#post380720

It was in response to what was in /var/log/messages when I tried to Burn the DVD
dyn1068542 kernal: cdrom : this disc doesn't have any tracks I recognise!

Disregard the sentence(s): "Ok. Good. This means your USB device is getting detected. You do not need any special drivers." and read from "What you need is to mount this device manually, since it's apparently not getting mounted by Redhat automatically." on

I tried that suggestion and No Go, it did not work and I receive an error
mount -t vfat /dev/dvd /mnt/usbdisk
mount: block device /dev/dvd is write-protected mounting read-only
moutn: dev/dvd: can't read superblock


As far as installing k3b goes, I can't get the installation to complete. When I run ./configure, I receive
checking build system type i686-pc-linux-gnu
checking host system type i686-pc-linus-gnu
checking target system type i686-pc-linux-gnu
checking for a BSD-compatiable install /usr/bin/install -c
checking for -p flag to install yes
checking whether build environment is sane yes
checking for gawk gawk
checking whether make sets $(MAKE) yes
checking for kde-config not found
configure errir the important program kde-config was not found. Please check whether you installed KDE correctly


Doing a find for kde results in nothing, kde is not present on the box (OS is Fedura Core 5).

So you're suggestion about installing k3b is appreciated, but so far no go with the installation

[lazlow]

Since you can read and write most files (corect?) mount is not the issue and the link does not apply.

You do not need kde to run k3b. In a terminal as root type: yum install k3b

As long as you have net acess there should be no problem

In FC you update and install with yum or yum based applications. Most (not all) software is available this way. It is only a rare occasion that you need to compile anything.

Lazlow

[quinlan]

Oh Okay, thanks. had no clue what "yum" meant.

[lazlow]

If that is true you probably really (really) need to update your system. One should update any fresh install just as soon as you are done installing. As root:

yum update yum (just avoids headaches)
yum update

If you have not updated since you installed, this will download a lot of stuff. Probably well over 100mb. Post back if you have trouble.

Lazlow

Edit: Did you try burning a single file renamed as .dat.x?

[quinlan]

No haven't tried burning a single file as .dat.x. I installed Fedora Core 5 on Monday of this week. How do I update the packages (the rpms)? yum update?
Thanks

[quinlan]

Oops never mind, running yum update as I write and it's updating all the packages. Should take awhile.

I know zip about Linux. I run the Solaris servers here.
Thanks for your help

[lazlow]

The Point I was trying to get to on changing the .dat to .dat.x is that the system MAY think that .dat is a special file type. It may be trying to burn it as filetype .dat (which appently cannot work with DVD). That is why when you burned two or more it could burn them. Basically the system said "Well, if there are two and he wants them to go to one disk they must just be regular files." This can occur with isos. You can burn a file.iso to a dvd, open the dvd and see file.iso. If you burn the iso and open the dvd, you will see the files in the iso.

Lazlow

[quinlan]

Can you open a file.iso on Windows without special ISO software? The original .dat files are on 8mm tapes, so I'm tarring them off the tape and then burning them on a DVD as .dat files. I know I can read a .dat file on windows as it's treated as a text file. Not so sure about .iso files. But I will try your suggestion when the package update is complete

Second question. How do I change the file type association in Fedora?