Can't eject a previously mounted CD?
If you are on debian i have noticed recently that gnomevfs (on unstable) requires famd. famd will open /cdrom after it is mounted and run a dir notification on it. now i think famd needs some fixing, firstly to not bother running dir notice on ro filesystems, and secondly allow an authorised user (other than the original program (in this case nautilus)) to drop specific mount point dirs from the notification list. so yes this is a userland problem as far as i can see.
matt
Quoted 7 lines · Matt
If you are on debian i have noticed recently that gnomevfs (on unstable) requires famd. famd will open /cdrom after it is mounted and run a dir notification on it. now i think famd needs some fixing, firstly to not bother running dir notice on ro filesystems, and secondly allow an authorised user (other than the original program (in this case nautilus)) to drop specific mount point dirs from the notification list. so yes this is a userland problem as far as i can see.
Yup.
But it sure is lame that our directory notification system (dnotify) needs to hold open a file descriptor on the directory, and thus really wrecks havoc on removable media.
Would be nice to have a saner replacement - for other reasons, too.
Rob Love
Quoted 7 lines · Rob Love
Quoted 1 line · Matt
If you are on debian i have noticed recently that gnomevfs (on unstable) requires famd. famd will open /cdrom after it is mounted and run a dir notification on it. now i think famd needs some fixing, firstly to not bother running dir notice on ro filesystems, and secondly allow an authorised user (other than the original program (in this case nautilus)) to drop specific mount point dirs from the notification list. so yes this is a userland problem as far as i can see.
Yup.
Quoted 9 lines
But it sure is lame that our directory notification system (dnotify) needs to hold open a file descriptor on the directory, and thus really wrecks havoc on removable media.
Would be nice to have a saner replacement - for other reasons, too.
Rob Love
This may be true for mounted media, but people are having these problems with audio cds too. And it doesn't explain why this never happened with any of the test kernels. does famd also mess with cds that are loaded and not mounted?
Quoted 14 lines · Ed Sweetman
Quoted 12 lines · Rob Love
Quoted 1 line · Matt
If you are on debian i have noticed recently that gnomevfs (on unstable) requires famd. famd will open /cdrom after it is mounted and run a dir notification on it. now i think famd needs some fixing, firstly to not bother running dir notice on ro filesystems, and secondly allow an authorised user (other than the original program (in this case nautilus)) to drop specific mount point dirs from the notification list. so yes this is a userland problem as far as i can see.
Yup.
But it sure is lame that our directory notification system (dnotify) needs to hold open a file descriptor on the directory, and thus really wrecks havoc on removable media.
Quoted 9 lines
Quoted 5 lines
Would be nice to have a saner replacement - for other reasons, too.
Rob Love
This may be true for mounted media, but people are having these problems with audio cds too. And it doesn't explain why this never happened with any of the test kernels. does famd also mess with cds that are loaded and not mounted?
Ack, just noticed that. I haven't seen famd messing with audio CDs, but also Joshua said that he didn't have famd installed on his machine, so that cuts that out. Strange how he said that eject(1) worked. Not sure, but just to reiterate to people though if you have mounted removable media it might not eject if you have famd installed on your machine, not sure if nautilus has been updated to drop its proxied dnotify when they are umounted.
Matt
Quoted 7 lines · Matt
If you are on debian i have noticed recently that gnomevfs (on unstable) requires famd. famd will open /cdrom after it is mounted and run a dir notification on it. now i think famd needs some fixing, firstly to not bother running dir notice on ro filesystems, and secondly allow an authorised user (other than the original program (in this case nautilus)) to drop specific mount point dirs from the notification list. so yes this is a userland problem as far as i can see.
I am using Debian. This is a good point. However, I have no component of fam installed on this Debian machine at all.
And why does the eject command work? I decided to strace it to see where it gets this invalid argument from..
open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 3
ioctl(3, 0x5309, 0xbffff948) = -1 EIO (Input/output error)
ioctl(3, FIBMAP, 0xbffff7f0) = 0
ioctl(3, FIBMAP, 0xbffff7f0) = 0
ioctl(3, FIBMAP, 0xbffff7f0) = 0
ioctl(3, BLKRRPART, 0xbffff7f0) = -1 EINVAL (Invalid argument)
ioctl(3, FDEJECT, 0xbffff948) = -1 EINVAL (Invalid argument)ioctl(3, SNDCTL_MIDI_MPUMODE, 0xbffff900) = -1 EINVAL (Invalid argument)
It wasn't as revealing as I thought it would be, but does this mean anything to someone more knowledgeable than I?
Note that as mentioned in a previous message, eject _does_ eject the CD.
Signature · 1 line
Joshua Kwan