Re: dvd+rw-tools 7.0: iso burning problem
I faced a problem with dvd+rw-tools (6.0, 6.1 und 7.0) when I tried to burn a DVD-Iso-Image to a dvd using the command line growisofs -Z /dev/scd2=/media/CDWserver/export/Server/DVD-Images/KNOPPIX_V5.0.1DVD-2006-06-01-DE.iso But it gives an invalid argument error: Output Executing 'builtin_dd if=/media/CDWserver/export/Server/DVD-Images/KNOPPIX_V5.0.1DVD-2006-06-01-DE.iso of=/dev/scd2 obs=32k seek=0' :-( write failed: Invalid argument The following command line works well: cat KNOPPIX_V5.0.1DVD-2006-06-01-DE.iso | growisofs -Z /dev/scd2=/dev/fd/0 Why is there is difference between these two commands. Why does the second work and the first not? I'd bet on the fact that growisofs opens file with O_DIRECT, while cat doesn't. For public reference. It turned to be the problem with ext3 implementation under 2.4 missing direct I/O method, which appears to be trivial [and erroneous] omission in kernel source [at lest ext2 implements this method]. One would normally expect O_DIRECT flag rejected already at open(2), but it doesn't seem to be the case. It remains mystery why it was not noticed earlier by 2.4 users. Next version shall compensate for this by banning O_DIRECT under 2.4 [naturally at run-time]. Meanwhile those who suffer from this can modify #ifdef O_DIRECT line in growisofs.c as #ifdef __notdef__ to work around the problem. A. P.S. for Marcus. The final conclusion slightly differs from one I gave you in private conversation, but it the workaround is the same. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dvd+rw-tools 7.0: iso burning problem
Hi, [...] problem with ext3 implementation under 2.4 [...] It remains mystery why it was not noticed earlier by 2.4 users. On my 2.4.21 kernel SuSE 9.0 and ext3 based /home there is no problem with growisofs 7.0 and this command: growisofs -Z /dev/sr1=/home/fertig.iso Shrug. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dvd+rw-tools 7.0: iso burning problem
Hi Thomas, Am Dienstag, 10. Oktober 2006 22:01 schrieb [EMAIL PROTECTED]: [...] problem with ext3 implementation under 2.4 [...] It remains mystery why it was not noticed earlier by 2.4 users. On my 2.4.21 kernel SuSE 9.0 and ext3 based /home there is no problem with growisofs 7.0 and this command: growisofs -Z /dev/sr1=/home/fertig.iso I found the problem on kernel 2.4.26 used by the german eisfair linux server project. It occurs with dvd-rw-tools 6.0-7.0. -- Gruss Marcus Marcus Roeckrath -- Vikarsbusch 8 -- D-48308 Senden -- Germany Phone : +49-2536-9944 -- Fax : +49-2536-9943 E-Mail : [EMAIL PROTECTED] WWW: http://home.foni.net/~marcusroeckrath/ pgpnZYJEyXTmJ.pgp Description: PGP signature
Re: dvd+rw-tools 7.0: iso burning problem
Hi Andy, Am Dienstag, 10. Oktober 2006 21:20 schrieb Andy Polyakov: It remains mystery why it was not noticed earlier by 2.4 users. I had written two reports on this mailinglist in june 2006 but got no comment on it. P.S. for Marcus. The final conclusion slightly differs from one I gave you in private conversation, but it the workaround is the same. Ok, I will wait for dvd+rw-tools 7.1 to compile a new package for the eisfair project. Till then I use the workaround you gave me in private mail: ifdef USE_O_DIRECT instead of ifdef O_DIRECT. -- Gruss Marcus Marcus Roeckrath -- Vikarsbusch 8 -- D-48308 Senden -- Germany Phone : +49-2536-9944 -- Fax : +49-2536-9943 E-Mail : [EMAIL PROTECTED] WWW: http://home.foni.net/~marcusroeckrath/ pgpgziVkSTeiD.pgp Description: PGP signature
Re: Request for cooperation with all burn backends
Thomas, this is a request towards all developers of burn backends. Is it possible we define a common locking mechanism for drives which does not depend on hardly documented Linux O_EXCL ? Something simple and very portable would be needed. I don't quite understand couple of things. As for locking, or rather serializing access to [relevant] devices. Very portable customarily means support for different operating systems. But the trouble is that the other systems, other than Linux that is, might and already do have own ways to serialize the access. It might be impossible and/or simply inappropriate not to use these mechanisms. Doesn't this kind of doom all very portable attempts as simply unachievable? Secondly. Why do you address back-end developers? Is it really a problem between recording programs? Isn't auto-mounting/-playing facilities interfering with ongoing recording *bigger* problem? So if you want to make the noble attempt and spend some time convincing developers time is better spent talking to that developers. IMHO that is:-) Advisory locking would be sufficient, i think. So shall we assume that we're actually talking about Linux and Linux only? At least the rest of *this* message implies Linux alone. Please keep it in mind... Have you seen resmgrd? Well, it didn't seem to catch up, but anyway... Why didn't it catch up? If you want my opinion, I think that all attempts to achieve the goal *purely* in user-land are doomed. 2.6 O_EXCL on block device appears to be sufficient for intended purpose and I personally would rather prefer it back-ported to 2.4 than some user-land facility. My motivation currently is about growisofs and /dev/srN : I had the ito open(2) O_EXCL those /dev/srN and /dev/scdM which have the same SCSI address as the /dev/sgK used by libburn. Note that it doesn't have to be /dev/sg. Even though different, both 2.4 and 2.6 provide interfaces for passing SCSI commands from user-land through /dev/cdrom. Well, I have to admit I've never tested CDROM_SEND_PACKET interface for non-data recordings... Did libburn developers do? I definitely would (if I were to develop non-data cd recording program:-). Addressing by block device is really more natural, because you share same view as auto-mounting/-playing and hot-plugging facilities and even initial OS installation procedure, and consequently even user view. Not to mention that that's how it works in most OSes anyway. To summarize. My vote goes for block device addressing, back-porting of O_EXCL to 2.4 and convincing auto-mounting/-playing developers to stick to it. My vote naturally doesn't make it just happen, but unfortunately I don't have time [or energy] to suggest alternative. Note that there are left-overs from experiment with resmsg in dvd+rw-tools code [look for dev_open], so in case of alternative outcome, I'd prefer to see something similar to that, i.e. link to an .so and if available modify behavior at run time. Cheers. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dvd+rw-tools 7.0: iso burning problem
It remains mystery why it was not noticed earlier by 2.4 users. I had written two reports on this mailinglist in june 2006 but got no comment on it. Sorry about that. Life does not always turn the way we like:-) Yet, you have to admit it's somewhat mysterious, because June is ~1/2 year[!] after first release utilizing O_DIRECT... Cheers. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
