Hide Forgot
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))')
Created attachment 528731 [details] File: anaconda-tb-jseIA3
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.
I cannot reproduce it now, it only occurred once and was reported by ABRT
Created attachment 531496 [details] anaconda logs This is reproduced with F16 Final RC5, this occurs sometimes.
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
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.
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
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?
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
What version of livecd-tools did you use? What parameters did you pass to litd?
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
can you check the label on the created partition? is it LIVE?