linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jim" <jim999@gmx.net>
To: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Kernel 2.4.26 cannot umount CD: device or resource busy (no fuser)
Date: Wed, 20 Jul 2005 01:58:06 +0200 (MEST)	[thread overview]
Message-ID: <29775.1121817486@www15.gmx.net> (raw)
In-Reply-To: 29450.1121817356@www6.gmx.net

Symptom: Cannot umount a CD-Rom in my CD-Roaster/Burner/Toaster whatever

Reason to write to ide AND Scsi-List: Its an IDE - Drive, but with
scsi-emulation running. So my 4 questions: WHY is the drive locked? And
HOW to work arround it other than to reboot the system? Can't a forced    
umount be implemented for other cases than just for NFS (as manpage 
sais)? Or is my system just too old and buggy? (because it is, besides from
updates)

And yes: It's more than once this happened:

# umount /mnt/toaster
umount: /mnt/toaster: device is busy
# fuser  -v -m /mnt/toaster/
# mount | grep toaster
/dev/scd0 on /mnt/toaster type iso9660 (ro,noexec,...)
# lsof | grep -e scd0 -e toaster
# umount /mnt/toaster
umount: /mnt/toaster: device is busy
# umount -f /mnt/toaster
umount2: Device or resource busy
umount: /dev/scd0: not mounted
umount: /mnt/toaster: Illegal seek
# umount /dev/scd0 || umount -f /dev/scd0
umount: /mnt/toaster: device is busy
umount2: Device or resource busy
umount: /dev/scd0: not mounted
umount: /mnt/toaster: Illegal seek
# umount -V
umount: mount-2.10m
# fuser -V
fuser from psmisc version 18
#


-- 
Greetings, Jim

-- 
Gruss, Jim

       reply	other threads:[~2005-07-19 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29450.1121817356@www6.gmx.net>
2005-07-19 23:58 ` Jim [this message]
2005-07-20  4:28   ` Kernel 2.4.26 cannot umount CD: device or resource busy (no fuser) Douglas Gilbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29775.1121817486@www15.gmx.net \
    --to=jim999@gmx.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).