Bug 529901 - Unable to re-read partition table
Summary: Unable to re-read partition table
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gparted
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-20 17:02 UTC by Michael Monreal
Modified: 2009-10-26 21:29 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-26 21:29:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 599078 0 None None None Never

Description Michael Monreal 2009-10-20 17:02:07 UTC
Every time I start gparted it greets me with a window telling me that "The kernel is unable to re-read the partition table on ..." and also tells me that I need to unmount all partitions on the device. 

This is nonsense because the drive contains the root filesystem, which will be mounted in nearly all cases (livecd excluded). Also, this has never been a problem in the past?

The console output is actually a bit more informative:

======================
libparted : 1.9.0
======================
The kernel was unable to re-read the partition table on /dev/sda (Device or resource busy).  This means Linux won't know anything about the modifications you made until you reboot.  You should reboot your computer before doing anything with /dev/sda.

Well, rebooting will of course mount some partitions on sda again.

Either don't show this messages or make it that gparted cannot be used on the drive it runs from.

Comment 1 Deji Akingunola 2009-10-20 22:43:14 UTC
The upstream developer is on the issue. The issue was reported upstream @ https://bugzilla.gnome.org/show_bug.cgi?id=599078

Comment 2 Deji Akingunola 2009-10-26 21:29:24 UTC
'Fixed' upstream. Fix will appear in future updated package.


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