Bug 150435 - RPM succeeds when trying to uninstall from a readonly filesystem
RPM succeeds when trying to uninstall from a readonly filesystem
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-03-06 09:17 EST by Ra P.
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-06 18:45:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ra P. 2005-03-06 09:17:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.7) Gecko/20040803 Firefox/0.9.3

Description of problem:

I have /usr mounted as read-only, and I only mount it read-write when I make changes to it.

However, I once forgot to mount it as R/W before trying to uninstall a package.  RPM just told me that it succeeded uninstalling the package when, in fact, it didn't succeed.

I realized the package wasn't uninstalled days later.

I don't know whether this is the intended behavior or not, but RPM should at least report something like:

- "Just for you to know, I couldn't uninstall [this_package] because the filesystem (is readonly / didn't allow me to)",

so one can either ignore the warning or make further necessary steps.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Mount /usr r/o
2. Uninstall any package installed
3. Check for uninstalled package.  It will still be there.

Actual Results:  RPM reported "Uninstall succeeded".

Expected Results:  RPM should have reported "Couldn't uninstall the package".

Additional info:
Comment 1 Jeff Johnson 2005-03-06 18:45:53 EST
Yep. rpm does not check for RO mounts, and rpm --erase is
"best effort" i.e. rpm will attempt to erase, but will
not terminate if a unlink(2) or rmdir(2) system call fails.

This behavior is as intended.

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