James Knott wrote:

James Knott wrote:

...

I'm trying to use KDar to make a backup to DVD-RW. However, as soon as K3B attempts to write the disk, I get an error message "Could not find growisofs executable.". However, that file, wtih permissions 755, is located in /usr/bin, which is one of the directories K3B is supposed to search.

If I try a DVD+R disk, I get an error "Could not determine size of resulting file.". The archive file is 4.3 GB, which should fit on either disk (4.7 GB).

Any suggestions?

tnx jk

Forgot to mention. This is with 64 bit SUSE 10.2

I have noticed that if I start K3B manually, it can find growisofs, but not when it's started by KDar. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan wrote:

* James Knott [12-31-06 17:22]:

...

I have noticed that if I start K3B manually, it can find growisofs, but not when it's started by KDar.

Doesn't this make you think that there might be a path problem? I would check that kdar has the full path to k3b, change the working directory for kdar, start kdar from a script denoting specific paths including /usr/bin/....

I suspect it's due to growisofs not wanting to run under sudo. I've been doing some testing and found that if I run KDar as a regular user, it works, though I have to keep the "slice" size below the default 4400 MB for DVD's. So far, 4000 works and I'm currently trying 4100. Also, running it as a user greatly limits what I can back up, so next I'll try logging in as root, instead of just runnning KDar as root. According to the growisofs man page, there is an option to allow it to be used under sudo, but recommends against it for security reasons. It's not a path issue, as /usr/bin is in root's path and K3B has no problem finding other files there. Also, K3B specifies the full path to the executables, so the PATH variable shouldn't even affect it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott wrote:

...

Patrick Shanahan wrote:

...

* James Knott [12-31-06 17:22]:

...

I have noticed that if I start K3B manually, it can find growisofs, but not when it's started by KDar.

Doesn't this make you think that there might be a path problem? I would check that kdar has the full path to k3b, change the working directory for kdar, start kdar from a script denoting specific paths including /usr/bin/....

I suspect it's due to growisofs not wanting to run under sudo. I've been doing some testing and found that if I run KDar as a regular user, it works, though I have to keep the "slice" size below the default 4400 MB for DVD's. So far, 4000 works and I'm currently trying 4100. Also, running it as a user greatly limits what I can back up, so next I'll try logging in as root, instead of just runnning KDar as root.

According to the growisofs man page, there is an option to allow it to be used under sudo, but recommends against it for security reasons. It's not a path issue, as /usr/bin is in root's path and K3B has no problem finding other files there. Also, K3B specifies the full path to the executables, so the PATH variable shouldn't even affect it.

Further on this. I can run KDar and burn DVD's, if I log in a root, but not if I run as root, from a user log in. I still haven't determined why I can't have a slice bigger than 4000 MB. This is interesting. I have run into a simular problem with Kdar on SUSE 10.0, On 12-19 Kdar worked fine, when I tried to back up /home it now tells me /media/dvdrecorder is not under /home/user please remove it. Only

James Knott wrote: trouble it is auto set and greyed out.If I su or run kdar as root from the run on kmenu it has the same result. I even uninstalled Kdar and am now in process of reinstalling it. Not sure what security updates I put on around the 20th od December. i will try root log in today since I'm trying to back up home before install 10.2. -- Russ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan wrote:

* James Knott [01-01-07 13:48]: [...]

...

Further on this. I can run KDar and burn DVD's, if I log in a root, but not if I run as root, from a user log in. I still haven't determined why I can't have a slice bigger than 4000 MB.

well, I cannot burn a 4.2G slice from dar. Presently generating a 4.0G slice to try, will report.

FWIW, when I create a 4000 MB slice, K3B shows it as 3.9 GB and 482 MB (IIRC) available. So, something is keeping K3B from writing to the full capacity of the DVD.

ps, kdar does not use the latest libdar-2.3.2-1.guru.suse101, so I am back to dar and cl.

ps1, kdar does not allow exclusion of dotted directories, ie: ~/.mozilla/default/Cache, but dar does.

ps2, you can put almost _all_ of the cl parameters for dar into ~/.darrc or /etc/darrc. Original setup a chore, but flying colors after.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan wrote:

* James Knott [01-01-07 14:29]: [...]

...

FWIW, when I create a 4000 MB slice, K3B shows it as 3.9 GB and 482 MB (IIRC) available. So, something is keeping K3B from writing to the full capacity of the DVD.

growisofs appears to be limited to 4G, that 4000*1024*1024. I have no problem writting <=4G. >4G growisofs faults.

16:16 wahoo:~ > rpm -qf `which growisofs` `which k3b` dvd+rw-tools-7.0-0.pm.0 k3b-0.12.17-100.pm.0

BUT, I have written >4G iso's ???

Perhaps growisofs is part of the creating the ISO process and can't exceed 4 GB. And perhaps K3B is capable of burning an ISO greater than 4 GB, once it has been created by other means. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* James Knott [01-01-07 16:45]: [...]

Another thing I've noticed is that doing backups this way causes my computer clock to run slow, despite running on an AMD 64 bit cpu and running ntpd.

I don't see that, amd 4200+ X2 ??? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* James Knott [01-01-07 18:09]: [...]

Are you burning the DVD at the same time? I burn one disk, while KDar is generating the next slice.

yes

(I wonder if the developer eats a lot of cold pizza? <g>)

nothing wrong with cold pizza, warm beer, or lukewarm coffee, but I know not ???

The clock slowdowns seem to appear when I'm doing both. It only loses a few minutes.

Mine is an AMD 64 3200+ single core & 1 GB memory.

Dual core makes the diff. I don't even notice the burning :^) -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-01-01 at 16:37 -0500, James Knott wrote:

Another thing I've noticed is that doing backups this way causes my computer clock to run slow, despite running on an AMD 64 bit cpu and running ntpd.

By running slow you mean that it shows a different hour, not that it skips numbers? That the command "date" shows the wrong hour? That's is indeed a bug. Whatever userspace programs do, even however busy the kernel is, it should not get the wrong hour. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFmZDjtTMYHG2NR9URAkV8AKCNY9c6+9kMh4XsTljlA3IPfCcVzQCfXd0o 0x302IA65I6/SFYfHGahlio= =ZbVu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-01-01 at 16:34 -0500, James Knott wrote:

...

growisofs appears to be limited to 4G, that 4000*1024*1024. I have no problem writting <=4G. >4G growisofs faults.

16:16 wahoo:~ > rpm -qf `which growisofs` `which k3b` dvd+rw-tools-7.0-0.pm.0 k3b-0.12.17-100.pm.0

BUT, I have written >4G iso's ???

Perhaps growisofs is part of the creating the ISO process and can't exceed 4 GB. And perhaps K3B is capable of burning an ISO greater than 4 GB, once it has been created by other means.

I have created bigger isos than 4GB using growisofs in the past. It's easy enough to test. nimrodel:/other/asnos # du -sh incoming/ 4.2G incoming/ nimrodel:/other/asnos # growisofs -dry-run -Z /dev/dvd -R ./incoming/ Executing 'mkisofs -R ./incoming/ | builtin_dd of=/dev/dvd obs=32k seek=0' INFO: UTF-8 character encoding detected by locale settings. Assuming UTF-8 encoded filenames on source filesystem, use -input-charset to override. Using BATTL000.SRT;1 for ./incoming/files/.... ... nimrodel:/other/asnos # No errors reported. I could check bigger sizes, but growisofs insists on checking the media size, it doesn't create image files. Actually, to create an image growisofs calls mkisofs. And, mkisofs will refuse to include a file bigger than 4 GB inside an iso image. I mean, it can not create an ISO image containing inside a file bigger than 4GB, which must be a limitation of the iso image format. However, the image itself can be bigger than 4GB. See the error you get: nimrodel:/biggy # growisofs -Z /dev/hdc /biggy/BIG.FILE -dvd-compat -speed=8 Executing 'mkisofs /biggy/BIG.FILE | builtin_dd of=/dev/hdc obs=32k seek=0' INFO: UTF-8 character encoding detected by locale settings. Assuming UTF-8 encoded filenames on source filesystem, use -input-charset to override. mkisofs: Value too large for defined data type. File /biggy/BIG.FILE is too large - ignoring <================ Total translation table size: 0 Total rockridge attributes bytes: 0 It may be that this is what you are observing. kdar is (I guess) creating backup archives bigger (slices?) than 4GB, which growisofs can't process. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFmZn5tTMYHG2NR9URAnqwAKCPpw5tqF0BrG6WSbk8sKqsMwPWswCfetVD zXQZZPSyoxphEDn5jPWrD3U= =7/L9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-01-01 at 18:35 -0500, James Knott wrote:

...

It may be that this is what you are observing. kdar is (I guess) creating backup archives bigger (slices?) than 4GB, which growisofs can't process.

Yes, that's what's happening. If I limit KDar to 4000 MB, it works. If 4100 MB, it fails. So, is it possible to fix mkisofs? I can understand a 4 GB limit with a 32 bit system, but I'm running 64 bits here.

No, it is not possible. As I understand the issue, it is not a limitation of mkisofs, but of the iso filesystem itself. Ie, you can burn 9GB images, but the files inside can not be bigger than 4Gb. It is different. A solution would be to convince dar to use some other image format, like XFS, for instance. Or raw. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFmaqKtTMYHG2NR9URAmFZAJ9Am41E3ZlYxq6FVCXHcUnoXCBi6wCdHWrb KhfzUD5EfMnj8z6EdsE+n9o= =8GpL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-01-01 at 18:58 -0500, Patrick Shanahan wrote:

[...]

...

It may be that this is what you are observing. kdar is (I guess) creating backup archives bigger (slices?) than 4GB, which growisofs can't process.

so a work-a-round to conserve dvd platter space would be to create 2.2G dar files and include 2 dar files per platter

Right. Or any combination yielding less than 4.7e9 bytes. Another way would be burning raw... no need for the image to be iso. I don't know how dar/kdar work, but I can guess. :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFmaj+tTMYHG2NR9URAvqkAKCRBr+Jg4cV3m1oMcTcvA+8y1pvPwCfSmC5 cP5Dg4VGTDTud9DMtPosV3A= =bz9w -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-01-02 at 14:38 -0600, Darryl Gregorash wrote:

...

FWIW, when I create a 4000 MB slice, K3B shows it as 3.9 GB and 482 MB As we already know, sizes depend on whether you are a programmer, or

On 2007-01-01 13:27, James Knott wrote: live in the real world:

4 GB = 4*1024 MB = 4096 MB, and 4000 MB = 4000/1024 GB = 3.906 GB

Actually, no. 4 GB = 4*1000 MB = 4000 MB and 4000 MB = 4000/1000 GB = 4.00 GB And: 4 GiB = 4*1024 MiB = 4096 MiB, and 4000 MiB = 4000/1024 GiB = 3.906 GiB Programmers are using the wrong units: prefixes like mega or giga were invented way earlier than programmers were born; they (we) must change and use the new names (mebibyte). The easiest reference I can find: http://en.wikipedia.org/wiki/MiB: | The unit was defined by the International Electrotechnical Commission | (IEC) in December 1998. Use of mebibyte and related units is strongly | endorsed by IEEE and CIPM. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFmurttTMYHG2NR9URAsxAAJ9qSFC8143V9a2jcnH8bek/jCF2XgCfexhX PoT9KaZK4skFbFOjSlo6lm4= =qPBR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-01-09 at 00:42 -0500, Digvijoy Chatterjee wrote:

On 1/2/07, Carlos E. R. <> wrote:

...

Programmers are using the wrong units: prefixes like mega or giga were invented way earlier than programmers were born; they (we) must change and use the new names (mebibyte).

linux-AMD:~ # growisofs -dry-run -Z /dev/dvd -R /home/digz/debian-31r4-amd64-binary-1.iso Executing 'mkisofs -R /home/digz/debian-31r4-amd64-binary-1.iso | builtin_dd of=/dev/dvd obs=32k seek=0' I: -input-charset not specified, using UTF-8 (detected in locale settings) mkisofs: Value too large for defined data type. File /home/digz/debian-31r4-amd64-binary-1.iso is too large

X86_64 growisofs does not support files greater than 4.0 G,

linux-AMD:~ # du -sch /home/digz/debian-31r4-amd64-binary-1.iso 4.4G /home/digz/debian-31r4-amd64-binary-1.iso

And, pray, how is this related to my previous post to which you are answering? Please, post your answers correctly. Ok, the thing is, with your syntax you are NOT burning the "/home/digz/debian-31r4-amd64-binary-1.iso" image. You are trying to create a new image that _contains_ the debian-31r4-amd64-binary-1.iso as a file - and that is impossible as the iso format does not support files bigger than 4GiB. Try this instead: growisofs -dry-run -dvd-compat -Z /dev/dvd=/home/digz/debian-31r4-amd64-binary-1.iso - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFo3vutTMYHG2NR9URAp2fAJ91Dm4S+9v/yTYpeQKhBFO0aFFoWACbBPkE L14/JfWn1P2jXXZWnN2dUWw= =hUi4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org