Bug 84206 - umount reports <garbled> as user needed to umount partition
umount reports <garbled> as user needed to umount partition
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: mount (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-13 09:10 EST by John Haxby
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-14 11:33:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Haxby 2003-02-13 09:10:40 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212

Description of problem:
If you attempt to umount a partition that you don't have permission to unmount
then you normally get a message like

   "umount: only root can umount ..."

but I get gibberish instead of the user name.

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


How reproducible:
Always

Steps to Reproduce:
1. umount /boot (as an ordinary user)
2.
3.
    

Actual Results:  umount: only U???\??? can unmount /dev/sda1 from /boot

on one system (resierfs) and

umount: only ???????? can unmount LABEL=/boot from /boot

on another (ext3 this time).


Expected Results:  I get this on a 7.3 system:

umount: only root can unmount LABEL=/boot from /boot


Additional info:

This is mount-2.11r-10
Comment 1 Elliot Lee 2003-08-13 16:57:15 EDT
Could you try the latest mount package (rawhide preferably, but RHL9 should work) and 
see if the problem goes away?
Comment 2 John Haxby 2003-08-14 04:51:35 EDT
On shrike with mount-2.11y-9 I get the message

   umount: only root can unmount LABEL=/boot from /boot

which would seem to be right and suggests that the problem has been fixed.

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