Bug 96532 - Error trying to open /dev/hdc exclusively (Device or resource busy)
Summary: Error trying to open /dev/hdc exclusively (Device or resource busy)
Status: RESOLVED NOT A BUG
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-07 16:42 UTC by cM0ss
Modified: 2005-01-07 20:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cM0ss 2005-01-07 16:42:07 UTC
Version:           0.11.16 (using KDE 3.2.3, Mandrake Linux Cooker i586 - Cooker)
Compiler:          gcc version 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)
OS:                Linux (i686) release 2.6.8.1-12mdksmp

In regular copy I get:
K3b can only copy CD-extra mixed mode cd's. and in the debugging output:
System
-----------------------
K3b Version:0.11.16 
KDE Version: 3.2.3
QT Version: 3.3.3


In clone I get:
Readcd returned error:16
error while reading disk
And the debugging output is:
System
-----------------------
K3b Version:0.11.16 
KDE Version: 3.2.3
QT Version: 3.3.3

readcd
-----------------------
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/hdc exclusively (Device or resource busy)... retrying in 1 second.
/usr/bin/readcd: Device or resource busy. Cannot open '/dev/hdc'. Cannot open SCSI driver.
/usr/bin/readcd: For possible targets try 'readcd -scanbus'.
/usr/bin/readcd: For possible transport specifiers try 'readcd dev=help'.

readcd comand:
-----------------------
/usr/bin/readcd -v dev=/dev/hdc f=/tmp/kde-mike/k3b_0.img -clone retries=128 


Have read through several other bug files online but have found nothing that seems to help me.
Comment 1 Sebastian Trueg 2005-01-07 18:31:22 UTC
not a k3b bug. probably automounting related. make sure no other app is using the drive.
Comment 2 cM0ss 2005-01-07 20:29:32 UTC
I think it is Mandrake specific. My wife's computer running the same MDK 10.1 gives exactly the same errors. Not sure if it is KDE problem or MDK.

Quote:not a k3b bug. probably automounting related. make sure no other app is using the drive.


Have tried setting the options to noauto and user, set the nosuid, unmask=0, and nodev. Still has the same issues. No other app is using it except the kde app that mounts it and asks if you want to browse or play.