From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262181AbTL2A23 (ORCPT ); Sun, 28 Dec 2003 19:28:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262186AbTL2A23 (ORCPT ); Sun, 28 Dec 2003 19:28:29 -0500 Received: from mx1.it.wmich.edu ([141.218.1.89]:64128 "EHLO mx1.it.wmich.edu") by vger.kernel.org with ESMTP id S262181AbTL2A21 (ORCPT ); Sun, 28 Dec 2003 19:28:27 -0500 Message-ID: <3FEF7528.1000301@wmich.edu> Date: Sun, 28 Dec 2003 19:28:24 -0500 From: Ed Sweetman User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3 X-Accept-Language: en MIME-Version: 1.0 To: Samuel Flory CC: Joshua Kwan , linux-kernel mailing list Subject: Re: Can't eject a previously mounted CD? References: <20031226081535.GB12871@triplehelix.org> <20031226103427.GB11127@ucw.cz> <20031226194457.GC12871@triplehelix.org> <3FEC91FA.1050705@rackable.com> <20031226202700.GD12871@triplehelix.org> <3FEF7359.9050900@rackable.com> In-Reply-To: <3FEF7359.9050900@rackable.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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.