Bug 746893

Summary: SystemError: (1, 'umount: /mnt/install/source: device is busy.\n (In some cases useful info about processes that use\n the device is found by lsof(8) or fuser(1))')
Product: [Fedora] Fedora Reporter: Hongqing Yang <hoyang>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, awilliam, jonathan, thomas.mey, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:35fa5040696ce366e177ea3fc4a4b9bc9d80ce5b3c3fe320fa8eaba99804ecab
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-19 14:26:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: anaconda-tb-jseIA3
none
anaconda logs
none
lsof output none

Description Hongqing Yang 2011-10-18 06:45:07 UTC
libreport version: 2.0.6
executable:     /usr/bin/python
hashmarkername: anaconda
kernel:         3.1.0-0.rc9.git0.0.fc16.x86_64
product:        Fedora
reason:         SystemError: (1, 'umount: /mnt/install/source: device is busy.\n        (In some cases useful info about processes that use\n         the device is found by lsof(8) or fuser(1))')
time:           Tue Oct 18 02:47:17 2011
version:        16-TC1

anaconda-tb-jseIA3: Binary file, 562326 bytes

description:
:The following was filed automatically by anaconda:
:anaconda 16.21 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/isys/__init__.py", line 152, in umount
:    rc = _isys.umount(what)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/yuminstall.py", line 1224, in complete
:    isys.umount(self.ayum.tree)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/installmethod.py", line 44, in doMethodComplete
:    anaconda.backend.complete(anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 241, in go_forward
:    self.dispatch()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked
:    self.anaconda.dispatch.go_forward()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
:    self.intf.icw.nextClicked()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1221, in handleRenderCallback
:    self.currentWindow.renderCallback()
:SystemError: (1, 'umount: /mnt/install/source: device is busy.\n        (In some cases useful info about processes that use\n         the device is found by lsof(8) or fuser(1))')

Comment 1 Hongqing Yang 2011-10-18 06:45:14 UTC
Created attachment 528731 [details]
File: anaconda-tb-jseIA3

Comment 2 Chris Lumens 2011-10-18 13:43:01 UTC
Can you determine what's got /mnt/install/source mounted?  My guess is something else has it automounted for us which is keeping it busy.  I've not seen any other reports like this for F16 so it seems unlikely it's something anaconda's doing wrong.

Comment 3 Hongqing Yang 2011-10-19 03:00:57 UTC
I cannot reproduce it now, it only occurred once and was reported by ABRT

Comment 4 Hongqing Yang 2011-11-03 07:10:55 UTC
Created attachment 531496 [details]
anaconda logs

This is reproduced with F16 Final RC5, this occurs sometimes.

Comment 5 Adam Williamson 2011-11-03 07:47:06 UTC
hongqing: when you see this can you try using lsof or fuser (as recommended by the error) to see what else is using /mnt/install/source ? Thanks!



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Hongqing Yang 2011-11-03 10:13:23 UTC
Created attachment 531539 [details]
lsof output

Finally, I hit it again.
The attachment is the output of command lsof
the fuser output is 230c or sth, I do not remember, and the history is discarded in dmsg, when I run it again, nothing in output.

Comment 7 Hongqing Yang 2011-11-03 11:36:10 UTC
Now I find the fuser /mnt/install/source is 465c.
ps aux |grep 465

root 465 0.0 0.0 13800 1856 tty2 Ss 07:27 0:00 /bin/bash  --login

Comment 8 Thomas Meyer 2012-06-01 21:26:07 UTC
Hi,

I'm hitting this bug while I tried to upgrade from Fedora 16 to 17 using an usb stick created with the livecd-iso-to-disk creator. Any ideas what's going on here? Do you need some special output/files to debug this?

Comment 9 Thomas Meyer 2012-06-01 21:30:24 UTC
lsof shows:

anaconda   571      root   62r      REG               8,17  11348917     106898 /run/install/source/Packages/g/glibc-common-2.15-37.fc17.x86_64.rpm
anaconda   571      root   63r      REG               8,17  11348917     106898 /run/install/source/Packages/g/glibc-common-2.15-37.fc17.x86_64.rpm
anaconda   986      root   62r      REG               8,17  11348917     106898 /run/install/source/Packages/g/glibc-common-2.15-37.fc17.x86_64.rpm
anaconda   986      root   63r      REG               8,17  11348917     106898 /run/install/source/Packages/g/glibc-common-2.15-37.fc17.x86_64.rpm

Comment 10 Adam Williamson 2012-06-02 02:04:06 UTC
What version of livecd-tools did you use? What parameters did you pass to litd?

Comment 11 Thomas Meyer 2012-06-02 08:40:56 UTC
it was either livecd-tools-16.15-1.fc16 or livecd-tools-17.11-1.fc17. I'm not sure if I first did upgrade my first machine of if I first created the usb stick.

The upgrade of the first machine had some trouble because of a duplicate installation of the fuse package. Why doesn't anaconda check against duplicate packages and warn/ask the user what to do?

I started the tool with:
$ sudo livecd-iso-to-disk /home/thomas/Downloads/Fedora-17-x86_64-DVD.iso /dev/sdc1

Comment 12 Adam Williamson 2012-06-03 22:08:39 UTC
can you check the label on the created partition? is it LIVE?