Re: Issues with cdrsin and USB devices on RHEL5
On Mon, 14 Jul 2008 15:24:32 +0200, "Thomas Schmitt" <scdbackup@gmx.net>
wrote:
>Hi,
>
>By default cdrskin will accept /dev/scdN or /dev/sgM but
>finally insists in seeing a /dev/srN.
>
>You may push it towards /dev/scdN by adding option
> drive_scsi_dev_family=scd
If I use
# cdrskin drive_scsi_dev_family=scd --devices
I get
====
cdrskin 0.4.8 : limited cdrecord compatibility wrapper for libburn
Note: If this hangs for a while then there is a drive with
unexpected problems (e.g. ill DMA).
One may exclude such a device file by removing r- and w-
permissions for all cdrskin users.
cdrskin: scanning for devices ...
*** buffer overflow detected ***: cdrskin terminated
======= Backtrace: =========
/lib/libc.so.6(__chk_fail+0x41)[0x8c4f21]
/lib/libc.so.6[0x8c4738]
/lib/libc.so.6(_IO_default_xsputn+0xcd)[0x84522d]
/lib/libc.so.6(_IO_vfprintf+0xd19)[0x81c529]
/lib/libc.so.6(__vsprintf_chk+0xad)[0x8c47ed]
/lib/libc.so.6(__sprintf_chk+0x30)[0x8c4720]
cdrskin[0x806e506]
cdrskin[0x805fd1e]
cdrskin[0x805cd84]
/lib/libpthread.so.0[0x9bb46b]
/lib/libc.so.6(clone+0x5e)[0x8b0dbe]
======= Memory map: ========
0034a000-0034b000 r-xp 0034a000 00:00 0 [vdso]
007c2000-007dc000 r-xp 00000000 03:02 124211 /lib/ld-2.5.so
007dc000-007dd000 r-xp 00019000 03:02 124211 /lib/ld-2.5.so
007dd000-007de000 rwxp 0001a000 03:02 124211 /lib/ld-2.5.so
007e0000-0091d000 r-xp 00000000 03:02 124238 /lib/libc-2.5.so
0091d000-0091f000 r-xp 0013c000 03:02 124238 /lib/libc-2.5.so
0091f000-00920000 rwxp 0013e000 03:02 124238 /lib/libc-2.5.so
00920000-00923000 rwxp 00920000 00:00 0
009b6000-009c9000 r-xp 00000000 03:02 124305 /lib/libpthread-2.5.so
009c9000-009ca000 r-xp 00012000 03:02 124305 /lib/libpthread-2.5.so
009ca000-009cb000 rwxp 00013000 03:02 124305 /lib/libpthread-2.5.so
009cb000-009cd000 rwxp 009cb000 00:00 0
00a41000-00a4c000 r-xp 00000000 03:02 124263
/lib/libgcc_s-4.1.2-20080102.so.1
00a4c000-00a4d000 rwxp 0000a000 03:02 124263
/lib/libgcc_s-4.1.2-20080102.so.1
08048000-08088000 r-xp 00000000 03:02 178440 /usr/bin/cdrskin
08088000-0808c000 rw-p 0003f000 03:02 178440 /usr/bin/cdrskin
0808c000-080dc000 rw-p 0808c000 00:00 0
0986d000-09893000 rw-p 0986d000 00:00 0
b7568000-b7569000 ---p b7568000 00:00 0
b7569000-b7f6b000 rw-p b7569000 00:00 0
b7f6f000-b7f70000 rw-p b7f6f000 00:00 0
bfc96000-bfcab000 rw-p bfc96000 00:00 0 [stack]
UNIX-SIGNAL: SIGABRT errno= 2
cdrskin: ABORT : Handling started. Please do not press CTRL+C now.
cdrskin: ABORT : Trying to ignore any further signals
cdrskin: ABORT : Abort processing depends on speed and buffer size
cdrskin: ABORT : Usually it is done with 4x speed after about a MINUTE
cdrskin: URGE : But wait at least the normal burning time before any kill
-9
cdrskin: ABORT : Drive is released and library is shut down now.
cdrskin: ABORT : Program done. Even if you do not see a shell prompt.
====
>
>> Note that hda is my hard disk, I don't know why cdrskin tries to use it.
>Now this /dev/hda is open O_EXCL and so libburn
>has no chance to examine it. A busy burner would
>look exactly the same.
On Linux you can check if an IDE device is disk or cdrom before doing
anything:
2.4, 2.6
# cat /proc/ide/hda/media
disk
# cat /proc/ide/hdc/media
cdrom
#
2.6 only:
# cat /sys/block/hda/device/media
disk
# cat /sys/block/hdc/device/media
cdrom
#
--
giulioo@pobox.com
Reply to: