Bug 895857
| Summary: | SystemError: (32, 'umount: /mnt/sysimage: target 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: | Jesse Brandeburg <jesse.brandeburg> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:4ae0e08fa7ad75d4d3cecf74cc58f7873f3a1f4c18dedeb767db61ac8aaad5ea | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-01-23 15:29:08 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jesse Brandeburg
2013-01-16 06:47:47 UTC
Created attachment 679390 [details]
File: anaconda-tb-vp42Vr
this bug was because my /etc/fstab was mounting ext3 filesystems as ext4. I had done this because I upgraded to an SSD and wanted FS trim support. I switched to F2 console and upgraded both partitions to ext4 with tune2fs command: tune2fs -O extents,uninit_bg,dir_index /dev/sdXy I rebooted and install is proceeding. the upgrade finished, but the bootloader was not updated with the new kernel, so the old kernel booted the new system successfully. I think that is an already known bug. I hope this bug report on F17 install is useful in fixing/preventing a bug in future upgrades, esp for users with long lived systems. You should definitely not be seeing this problem with upgrades to F18, given that we are using a completely new upgrade process that uses system tools instead of anaconda, and those tools should understand your /etc/fstab better. Thanks for the report. |