[Bug 1010176] [NEW] casper toram doesn't free /dev/loop0 after copy

[Alex Roper]

Public bug reported:

When booting Ubuntu 12.04 livecd using the "toram" option to copy the CD
image into RAM before proceeding, casper mounts the imstallation media
at /isodevice at boot. This device is no longer necessary once the image
copy is complete, and therefore unmounting it should work if requested
by the user.

However, attempting to umount it fails claiming it is busy, yet fuser -m
provides nothing. It turns out that /dev/loop0 is still bound to the
image stored on /isodevice.

I agree it's perfectly reasonable to keep /isodevice mounted after boot
toram in case the user wants something on there, but it should be easy
via gui or cli to umount it, and since the loopback doesn't show in lsof
or fuser -m, many intermediate users are going to be stumped by this.

Since yanking the device anyway doesn't cause any problems, I would
consider this a minor bug concerned primarily with user friendliness.

** Affects: casper (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1010176

Title:
  casper toram doesn't free /dev/loop0 after copy

Status in “casper” package in Ubuntu:
  New

Bug description:
  When booting Ubuntu 12.04 livecd using the "toram" option to copy the
  CD image into RAM before proceeding, casper mounts the imstallation
  media at /isodevice at boot. This device is no longer necessary once
  the image copy is complete, and therefore unmounting it should work if
  requested by the user.

  However, attempting to umount it fails claiming it is busy, yet fuser
  -m provides nothing. It turns out that /dev/loop0 is still bound to
  the image stored on /isodevice.

  I agree it's perfectly reasonable to keep /isodevice mounted after
  boot toram in case the user wants something on there, but it should be
  easy via gui or cli to umount it, and since the loopback doesn't show
  in lsof or fuser -m, many intermediate users are going to be stumped
  by this.

  Since yanking the device anyway doesn't cause any problems, I would
  consider this a minor bug concerned primarily with user friendliness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1010176/+subscriptions