[Nottingham] CDROM weirdness

[stripes theotoky]

I am running

Operating System: Debian GNU/Linux stretch/sid
Kernel: Linux 3.1.0-1-amd64
Architecture:  x86-64
KDE version: 4.14.2

I have been away for a couple of months, came home and applied about 1,000
updates with the result that after the box is booted the first CD or DVD
put in the drive will automount and behave normally. Once this disk is
ejected the drive will not recognise any disk including the one it just
read ok.

The messages from

grep sr0 /var/log/messages | tail

Might give a clue if I could work out what they meant.


Jun 14 19:30:20 localhost kernel: [36387.839333] sr0: CDROM not ready.
Make sure there is a disc in the drive.
Jun 14 19:30:20 localhost kernel: [36387.841019] sr0: CDROM not ready.
Make sure there is a disc in the drive.
Jun 14 19:30:20 localhost kernel: [36387.842811] sr0: CDROM not ready.
Make sure there is a disc in the drive.
Jun 14 19:30:20 localhost kernel: [36387.844691] sr0: CDROM not ready.
Make sure there is a disc in the drive.
Jun 14 19:30:20 localhost kernel: [36387.846354] sr0: CDROM not ready.
Make sure there is a disc in the drive.
Jun 17 14:28:09 localhost kernel: [277457.432345] VFS: busy inodes on
changed media or resized disk sr0
Jun 17 14:30:42 localhost kernel: [277609.957584] VFS: busy inodes on
changed media or resized disk sr0
Jun 17 17:22:39 localhost kernel: [    1.960270] sr0: scsi3-mmc drive:
48x/48x writer dvd-ram cd/rw xa/form2 cdda
tray

Jun 17 17:27:50 localhost kernel: [  333.794856] VFS: busy inodes on
changed media or resized disk
sr0

Jun 17 17:28:33 localhost kernel: [  376.805648] VFS: busy inodes on
changed media or resized disk sr0

I could of course just reboot the box everytime I wanted to change a CD but
as I have about 100 to sort through and throw out that is not really a goer.

I assumed probably a lock file in /tmp that wasn't clearing but can't find
anything there that looks likely, any ideas?

This was working until the updates this week but as there were so many of
them I wouldn't evern be able to guess at what might have broken it.

Regards
Stripes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/nottingham/attachments/20150617/0e78a19f/attachment.html>