public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Samuel Flory <sflory@rackable.com>
Cc: Joshua Kwan <joshk@triplehelix.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Can't eject a previously mounted CD?
Date: Sun, 28 Dec 2003 19:28:24 -0500	[thread overview]
Message-ID: <3FEF7528.1000301@wmich.edu> (raw)
In-Reply-To: <3FEF7359.9050900@rackable.com>

Samuel Flory wrote:
> Joshua Kwan wrote:
> 
>> On Fri, Dec 26, 2003 at 11:54:34AM -0800, Samuel Flory wrote:
>>
>>>  What does fuser -kv /mnt/cdrom claim?
>>
>>
>>
>> It's /cdrom here. I tried it on both /cdrom and /dev/cdrom after
>> unmounting it, and the output was blank.
>>
>> While mounted, here was the output:
>>
>>                      USER        PID ACCESS COMMAND
>> /cdrom               root     kernel mount  /cdrom
>> No automatic removal. Please use  umount /cdrom
>>
>> I guess that doesn't say much though...
>>
> 
>   It does seem to imply that the cdrom is still mounted, or that 
> something thinks it's still mounted.


I dont believe this unable to eject problem has anything to do with 
anything thinking it's mounted.

famd upon load seems to cause this error.
end_request: I/O error, dev hdc, sector 0

That's my cdrom.  Perhaps the kernel has a bug in the code dealing with 
an access to the cdrom where no media is mounted and/or loaded.  Either 
way, this is at boot and seems to be a kernel bug initiated by FAM. At 
least the version distributed with debian-unstable.  I dont use gnome (i 
do have some gnome programs installed to test on) and the error message 
was reported soon after the loading of FAM.


  reply	other threads:[~2003-12-29  0:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26  8:15 Can't eject a previously mounted CD? Joshua Kwan
2003-12-26 10:34 ` Vojtech Pavlik
2003-12-26 19:44   ` Joshua Kwan
2003-12-26 19:54     ` Samuel Flory
2003-12-26 20:27       ` Joshua Kwan
2003-12-26 23:26         ` Ed Sweetman
2003-12-26 23:56           ` Nuno Silva
2003-12-27  2:28             ` Joshua Kwan
2003-12-29  0:20         ` Samuel Flory
2003-12-29  0:28           ` Ed Sweetman [this message]
2003-12-29  1:36             ` Ed Sweetman
  -- strict thread matches above, loose matches on Subject: below --
2003-12-27  0:31 Matt
2003-12-27  0:44 ` Rob Love
2003-12-27  1:13   ` Ed Sweetman
2003-12-27 15:11     ` Matt
2003-12-27  3:12 ` Joshua Kwan
2003-12-29  1:56 Walt H
2003-12-29  2:04 ` Ed Sweetman
2003-12-29  3:45   ` Walt H
2003-12-29  6:23     ` Ed Sweetman
2003-12-29  7:41       ` Ed Sweetman
2003-12-29  7:56     ` Ed Sweetman
2003-12-29 16:36       ` Walt H
2003-12-29 17:53         ` Ed Sweetman
2003-12-29 18:05           ` Walt H
2003-12-29 19:23           ` Walt H
2003-12-29 19:40             ` Jens Axboe

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=3FEF7528.1000301@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --cc=joshk@triplehelix.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sflory@rackable.com \
    /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