Bug 808109 - DVD mount issues after update
Summary: DVD mount issues after update
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
: 806909 808121 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2012-03-29 15:27 UTC by guna_pmk
Modified: 2013-02-14 01:28 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-02-14 01:28:07 UTC
Type: ---

Attachments (Terms of Use)

Description guna_pmk 2012-03-29 15:27:09 UTC
Description of problem:

Since my last update I have my backup system (to a dvd) broken. No link is created for cdrom and dvd.

This is the update details (result of yum history info 63):
Loaded plugins: langpacks, presto, refresh-packagekit
Transaction ID : 63
Begin time     : Tue Mar 27 14:51:24 2012
Begin rpmdb    : 1599:eb10d0ff66ebec3e5830f695c242ad13e5295aad
End time       :            14:52:39 2012 (75 seconds)
End rpmdb      : 1599:5f55d6af9205ff432c6631404531b8c562552608
User           : System <unset>
Return-Code    : Success
Transaction performed with:
    Installed     PackageKit-yum-0.6.21-2.fc16.x86_64     @updates
    Installed     rpm-               @updates
    Installed     yum-3.4.3-7.fc16.noarch                 @updates
    Installed     yum-metadata-parser-1.1.4-5.fc16.x86_64 @koji-override-0/$releasever
    Installed     yum-presto-0.7.1-1.fc16.noarch          @koji-override-0/$releasever
Packages Altered:
    Updated audit-2.1.3-4.fc16.x86_64                      @?fedora
    Update        2.2-1.fc16.x86_64                        @updates
    Updated audit-libs-2.1.3-4.fc16.x86_64                 @?fedora
    Update             2.2-1.fc16.x86_64                   @updates
    Updated audit-libs-python-2.1.3-4.fc16.x86_64          @?fedora
    Update                    2.2-1.fc16.x86_64            @updates
    Updated bash-4.2.20-1.fc16.x86_64                      ?
    Update       4.2.24-1.fc16.x86_64                      @updates
    Updated chkconfig-1.3.57-3.fc16.x86_64                 ?
    Update            1.3.59-1.fc16.x86_64                 @updates
    Updated cpp-4.6.2-1.fc16.x86_64                        @?fedora
    Update      4.6.3-2.fc16.x86_64                        @updates
    Updated cups-1:1.5.2-1.fc16.x86_64                     ?
    Update       1:1.5.2-6.fc16.x86_64                     @updates
    Updated cups-libs-1:1.5.2-1.fc16.x86_64                ?
    Update            1:1.5.2-6.fc16.x86_64                @updates
    Updated curl-7.21.7-6.fc16.x86_64                      ?
    Update       7.21.7-7.fc16.x86_64                      @updates
    Updated dash-0.5.6-6.fc16.x86_64                       ?
    Update       0.5.7-1.fc16.x86_64                       @updates
    Updated exempi-2.1.1-2.fc15.x86_64                     @?fedora
    Update         2.2.0-1.fc16.x86_64                     @updates
    Updated foomatic-filters-4.0.8-4.fc16.x86_64           @?fedora
    Update                   4.0.8-8.fc16.x86_64           @updates
    Updated gcc-4.6.2-1.fc16.x86_64                        @?fedora
    Update      4.6.3-2.fc16.x86_64                        @updates
    Updated gcc-c++-4.6.2-1.fc16.x86_64                    @?fedora
    Update          4.6.3-2.fc16.x86_64                    @updates
    Updated gcc-gfortran-4.6.2-1.fc16.x86_64               @?fedora
    Update               4.6.3-2.fc16.x86_64               @updates
    Updated google-chrome-beta-18.0.1025.113-127419.x86_64 ?
    Update                     18.0.1025.140-128625.x86_64 ?
    Updated libcurl-7.21.7-6.fc16.x86_64                   ?
    Update          7.21.7-7.fc16.x86_64                   @updates
    Updated libgcc-4.6.2-1.fc16.i686                       @?fedora
    Updated libgcc-4.6.2-1.fc16.x86_64                     @?fedora
    Update         4.6.3-2.fc16.i686                       @updates
    Update         4.6.3-2.fc16.x86_64                     @updates
    Updated libgfortran-4.6.2-1.fc16.x86_64                @?fedora
    Update              4.6.3-2.fc16.x86_64                @updates
    Updated libgomp-4.6.2-1.fc16.x86_64                    @?fedora
    Update          4.6.3-2.fc16.x86_64                    @updates
    Updated libjpeg-turbo-1.1.1-3.fc16.i686                ?
    Updated libjpeg-turbo-1.1.1-3.fc16.x86_64              ?
    Update                1.2.0-1.fc16.i686                @updates
    Update                1.2.0-1.fc16.x86_64              @updates
    Updated libquadmath-4.6.2-1.fc16.x86_64                @?fedora
    Update              4.6.3-2.fc16.x86_64                @updates
    Updated libquadmath-devel-4.6.2-1.fc16.x86_64          @?fedora
    Update                    4.6.3-2.fc16.x86_64          @updates
    Updated libquvi-scripts-0.4.2-1.fc16.noarch            ?
    Update                  0.4.3-1.fc16.noarch            @updates
    Updated libssh2-1.2.7-1.fc15.x86_64                    @?fedora
    Update          1.2.7-4.fc16.x86_64                    @updates
    Updated libstdc++-4.6.2-1.fc16.i686                    @?fedora
    Updated libstdc++-4.6.2-1.fc16.x86_64                  @?fedora
    Update            4.6.3-2.fc16.i686                    @updates
    Update            4.6.3-2.fc16.x86_64                  @updates
    Updated libstdc++-devel-4.6.2-1.fc16.i686              @?fedora
    Updated libstdc++-devel-4.6.2-1.fc16.x86_64            @?fedora
    Update                  4.6.3-2.fc16.i686              @updates
    Update                  4.6.3-2.fc16.x86_64            @updates
    Updated libtool-2.4-8.fc16.x86_64                      ?
    Update          2.4-9.fc16.x86_64                      @updates
    Updated libtool-ltdl-2.4-8.fc16.i686                   ?
    Updated libtool-ltdl-2.4-8.fc16.x86_64                 ?
    Update               2.4-9.fc16.i686                   @updates
    Update               2.4-9.fc16.x86_64                 @updates
    Updated libuser-0.57.2-1.fc16.x86_64                   @?fedora
    Update          0.57.4-1.fc16.x86_64                   @updates
    Updated libuser-python-0.57.2-1.fc16.x86_64            @?fedora
    Update                 0.57.4-1.fc16.x86_64            @updates
    Updated lohit-assamese-fonts-2.5.0-1.fc16.noarch       @?fedora
    Update                       2.5.1-1.fc16.noarch       @updates
    Updated lohit-bengali-fonts-2.5.0-1.fc16.noarch        @?fedora
    Update                      2.5.1-1.fc16.noarch        @updates
    Updated lohit-gujarati-fonts-2.5.0-1.fc16.noarch       @?fedora
    Update                       2.5.1-1.fc16.noarch       @updates
    Updated lohit-kannada-fonts-2.5.0-1.fc16.noarch        @?fedora
    Update                      2.5.1-1.fc16.noarch        @updates
    Updated lohit-oriya-fonts-2.5.0-1.fc16.noarch          @?fedora
    Update                    2.5.1-1.fc16.noarch          @updates
    Updated lohit-punjabi-fonts-2.5.0-2.fc16.noarch        ?
    Update                      2.5.1-1.fc16.noarch        @updates
    Updated lohit-telugu-fonts-2.4.5-13.fc16.noarch        @?fedora
    Update                     2.5.1-1.fc16.noarch         @updates
    Updated nfs-utils-1:1.2.5-4.fc16.x86_64                ?
    Update            1:1.2.5-5.fc16.x86_64                @updates
    Updated psmisc-22.13-8.fc15.x86_64                     @?fedora
    Update         22.16-1.fc16.x86_64                     @updates
    Updated quvi-0.4.1-1.fc16.x86_64                       ?
    Update       0.4.2-1.fc16.x86_64                       @updates
    Updated selinux-policy-3.10.0-75.fc16.noarch           ?
    Update                 3.10.0-80.fc16.noarch           @updates
    Updated selinux-policy-targeted-3.10.0-75.fc16.noarch  ?
    Update                          3.10.0-80.fc16.noarch  @updates
    Updated tzdata-2012b-1.fc16.noarch                     ?
    Update         2012b-3.fc16.noarch                     @updates
    Updated tzdata-java-2012b-1.fc16.noarch                ?
    Update              2012b-3.fc16.noarch                @updates
    Updated xorg-x11-server-Xephyr-1.11.4-1.fc16.x86_64    ?
    Update                         1.11.4-2.fc16.x86_64    @updates
    Updated xorg-x11-server-Xorg-1.11.4-1.fc16.x86_64      ?
    Update                       1.11.4-2.fc16.x86_64      @updates
    Updated xorg-x11-server-common-1.11.4-1.fc16.x86_64    ?
    Update                         1.11.4-2.fc16.x86_64    @updates
Scriptlet output:
   1 SELinux:  Could not downgrade policy file /etc/selinux/targeted/policy/policy.26, searching for an older version.
   2 SELinux:  Could not open policy file <= /etc/selinux/targeted/policy/policy.26:  No such file or directory
   3 load_policy:  Can't load policy:  No such file or directory
history info

I can see the following in the /var/log/messages (dont know what exactly caused these error messages; all I was dong at this time was eject, eject-t and a mount /dev/dvd):

Mar 29 15:00:25 hostname kernel: [15817.472165] EXT4-fs (sr0): VFS: Can't find ext4 filesystem
Mar 29 15:00:25 hostname kernel: [15817.495814] EXT4-fs (sr0): VFS: Can't find ext4 filesystem
Mar 29 15:00:25 hostname kernel: [15817.519424] EXT4-fs (sr0): VFS: Can't find ext4 filesystem
Mar 29 15:00:25 hostname kernel: [15817.637546] ISOFS: Unable to identify CD-ROM format.
Mar 29 15:00:25 hostname kernel: [15817.711226] FAT-fs (sr0): bogus number of reserved sectors
Mar 29 15:00:25 hostname kernel: [15817.711233] FAT-fs (sr0): Can't find a valid FAT filesystem
Mar 29 15:00:25 hostname kernel: [15817.757931] hfs: can't find a HFS filesystem on dev sr0.
Mar 29 15:00:25 hostname kernel: [15817.812323] hfs: unable to find HFS+ superblock

This was working until the last update on 27th Mar.

This is the result of uname -a

Linux hostname 3.3.0-4.fc16.x86_64 #1 SMP Tue Mar 20 18:05:40 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Have not noticed (yet) any other issues after this update.

Please let me know if you need more information in this regard.


Comment 1 guna_pmk 2012-03-30 08:27:04 UTC
Not sure whether I have explained it correctly in my original request. Some more here.

After the above said update there are no links /dev/cdrom /dev/dvd pointing to /dev/sr0 anymore.

When I issue eject (just eject from the command line) I get an error 

eject: unable to find or open device for: `cdrom' 

(as there is no cdrom link); but if I issue /dev/sr0 it works.

There are links /dev/dvd2 and /dev/dvdrw2 pointing to /dev/sr0.

The nautilus file manager mounts without any problem when a dvd is inserted.

What is the standard way to mount cd/dvd/bd in Fedora(in my case F16 64 bit) with Gnome (in my case Gnome 3)? Should I change my script always to use /dev/sr0 instead of /dev/dvd (or /dev/cdrom)? Will /dev/sr0 not change?

After all there was no problem until the above said software update. But I also can agree that it may be something different from the software update.


Comment 2 Tim Waugh 2012-03-30 08:32:16 UTC
Please try the procedure detailed in bug #747114 comment #7.

*** This bug has been marked as a duplicate of bug 747114 ***

Comment 3 Tim Waugh 2012-04-02 12:12:09 UTC
This seems to be different than the original cause of bug #747114 as it pre-dates the cups "PrivateTmp" change.  Marking this as not a duplicate.

Comment 4 Tim Waugh 2012-04-02 12:12:51 UTC
*** Bug 806909 has been marked as a duplicate of this bug. ***

Comment 5 Tim Waugh 2012-04-02 12:13:10 UTC
*** Bug 808121 has been marked as a duplicate of this bug. ***

Comment 6 guna_pmk 2012-04-03 12:49:17 UTC
Well, now there is a development in this issue; actually more trouble. After a write operation to the disc, I keep seeing the following in the /var/log/messages: 

Apr  2 09:30:29 hostname kernel: [340798.622317] VFS: busy inodes on changed media or resized disk sr0
Apr  2 09:30:32 hostname kernel: [340801.845138] VFS: busy inodes on changed media or resized disk sr0
Apr  2 09:31:52 hostname kernel: [340881.552248] VFS: busy inodes on changed media or resized disk sr0

and if I try to write to another disc with growisofs I see the following error:

:-( unable to O_EXCL /dev/sr0: someone was in time to remount?

To get the disc writing (at least once) I have to reboot the machine (I dont know which service that I should restart - I just reboot the machine).

Is this related to the original issue?


Comment 7 Tim Waugh 2012-04-03 15:15:57 UTC
What does 'rpm -q cups' say?

Comment 8 guna_pmk 2012-04-04 08:57:12 UTC

Comment 9 Tim Waugh 2012-04-04 10:54:01 UTC
Could you please try with the test update cups-1.5.2-8.1.fc16?  See bug #807672 comment #12.

Comment 10 guna_pmk 2012-04-05 14:52:30 UTC
I have installed the package. It did not fix the problem Tim.

Comment 11 Tim Waugh 2012-04-10 10:47:17 UTC
Thanks. (Did you try rebooting? Expect so...)

Now could you please try downgrading CUPS to this version?: 1.5.2-1.fc16
Packages are here:

Just download the relevant packages for your architecture and then run:

yum downgrade ./cups-*1.5.2-1.fc16.*.rpm

After rebooting, does the problem persist?

Comment 12 guna_pmk 2012-04-10 16:40:17 UTC
Hi Tim,

The commands 

yum downgrade ./cups-*1.5.2-1.fc16.*.rpm
yum downgrade cups-*1.5.2-1.fc16.*.rpm

failed with 

Loaded plugins: langpacks, presto, refresh-packagekit
No package ./cups-*1.5.2-1.fc16.*.rpm available.
Error: Nothing to do

Any other suggestions?


Comment 13 Jiri Popelka 2012-04-11 07:58:54 UTC
'yum downgrade cups*.rpm' works for me

Comment 14 Tim Waugh 2012-04-11 08:21:45 UTC
guna_pmk: you downloaded the packages?

Comment 15 guna_pmk 2012-04-11 09:51:50 UTC
My apologies Tim. I tried it before finishing the work and completely missed your download instructions. I have downloaded and downgraded cups successfully and tried again; the problem seems to be there still.

I think I have mentioned all the following previously; just to recap:

1. After a reboot, a dvd write works without a problem
2. Once a dvd is written ( I use growisofs for writing), the next one fails most of the time. It works sometime. But it is very inconsistent. All the times it fails to write, there is these lines in the /var/log/messages
    VFS: busy inodes on changed media or resized disk sr0
3. All this happens since my software update on 2012-03-29.
4. Since the a software update, I also have no links (/dev/dvd, /dev/dvdrw or /dev/cdrom) created pointing to /dev/sr0 (or whatever the dvd device is); but there are /dev/dvd2, /dev/dvdrw2, /dev/cdrom2 and /dev/cdrw2 links pointing to /dev/sr0.

Additionally, following is the contents of my /etc/udev/rules.d/70-persistent-cd.rules:
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.

# ATAPI_iHBS212_2 (pci-0000:00:1f.2-scsi-1:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"

# CD-ROM (pci-0000:00:1d.0-usb-0:1.6:1.0-scsi-0:0:0:1)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="SEMC_CD-ROM_42583930324251573159-0:1", SYMLINK+="cdrom1", ENV{GENERATED}="1"

# ATAPI_iHBS212_2 (pci-0000:00:1f.2-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-0:0:0:0", SYMLINK+="cdrom2", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-0:0:0:0", SYMLINK+="cdrw2", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-0:0:0:0", SYMLINK+="dvd2", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-0:0:0:0", SYMLINK+="dvdrw2", ENV{GENERATED}="1"

Does the above ring any bell?

Please let me know if you need more information in this regard.


Comment 16 guna_pmk 2012-04-11 11:24:45 UTC
Hi Tim,

More problems here. Not sure whether the latest downgrade caused the problem. But I have not encountered this problem earlier. I have a UDF image file which I mount to store and remove files. 

Now even after umounting, the loop device is not detached. But if I stop cups, the loop device is detached. But the previously stuck devices can not be retrieved. This is exactly the same as issue #758159.

I mount the image as follows:

mount -o loop /path/to/image.iso /mnt/image

to unmount:

umount /mnt/image


Comment 17 Tim Waugh 2012-04-16 10:40:53 UTC
Your most recent comment refers to bug #758159, which is an unresolved kernel bug.  However, in comment #15 you referred to a problem (after writing a DVD) which goes away when cups is not running.

When you tried cups-1.5.2-8.1.fc16, did you reboot before trying the DVD?  Please humour me, and try again: the 1.5.2-8.1 package is now a stable update and should be available either now or in the next couple of days.

Once you have cups-1.5.2-8.1.fc16 installed, reboot the machine and try your test again.

If you are still seeing "busy inodes" messages, could you please run "mount" to see if the disc is mounted?  If so, could you please run "fuser -mv /mnt/..." on the mount-point and find out which processes are keeping the file system mounted?

Comment 18 guna_pmk 2012-04-18 08:36:44 UTC
Hi Tim,

Sorry for the delay. I was away for some time.

To answer your questions,

"However, in comment #15 you referred to a problem (after writing a DVD)
which goes away when cups is not running." - I could not see any mention about cups in comment #15 Tim. I don't get the point here.

"When you tried cups-1.5.2-8.1.fc16, did you reboot before trying the DVD? " - Yes I did Tim.

I now have the latest cups (I have performed a complete system update). My new kernel is 3.3.1-5.fc16.x86_64. But it is still incosistent.

"If you are still seeing "busy inodes" messages, could you please run "mount" to
see if the disc is mounted?  If so, could you please run "fuser -mv /mnt/..."
on the mount-point and find out which processes are keeping the file system
mounted?" - That was the first thing I did when I saw the error messages. I even tried 

ls -l /proc/*/cwd | grep -i "cd\|dvd\|sr?"

The dvd device was not in use by any process.

Besides, testing this issue takes all my time; all I do now is reboot the machine once the disc is written. It is very disappointing :(.

We also have not found out the issue with the udev rules :(.


Comment 19 Tim Waugh 2012-04-23 11:03:07 UTC
OK.  Sorry, I must have mis-read the comment.

So I don't think cups is related to this problem any more.

Changing component to kernel.

Comment 20 Mark 2012-05-16 05:48:42 UTC
I also upgraded a kernel and suddenly /dev/dvd disappeared but /dev/dvd2 pointed to sr0.  Looks something caused a different scsi address to be used for the same hardware...

< # ATAPI_iHBS212_2 (pci-0000:00:1f.2-scsi-1:0:0:0)
> # ATAPI_iHBS212_2 (pci-0000:00:1f.2-scsi-0:0:0:0)

< # HL-DT-STDVD+-RW_GSA-H31N (pci-0000:00:1f.2-scsi-4:0:0:0)
> # HL-DT-STDVD+-RW_GSA-H31N (pci-0000:00:1f.2-scsi-0:0:0:0)

I removed both sets of rules from /etc/udev/70-persistent-cd.rules and ran:
service udev restart

Now 70-persistent-cd.rules has just one set of rules for the DVD drive and /dev/dvd is back.

Comment 21 Dave Jones 2012-10-23 15:40:32 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 22 Mads Kiilerich 2012-10-23 18:52:02 UTC
Isn't this the systemd namespace issue?

Comment 23 Fedora End Of Life 2013-01-16 22:57:49 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 24 Fedora End Of Life 2013-02-14 01:28:11 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.