Bug 444355 - fsadm fails - readlink does not support options -e -n
Summary: fsadm fails - readlink does not support options -e -n
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lvm2
Version: 4.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: Corey Marthaler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-27 17:57 UTC by Milan Broz
Modified: 2013-03-01 04:06 UTC (History)
8 users (show)

Fixed In Version: RHBA-2008-0776
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-24 20:08:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0776 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2008-07-23 17:19:45 UTC

Description Milan Broz 2008-04-27 17:57:59 UTC
Description of problem:
fsadm doesn't work on RHEL4.6 (not sure if update of some package 

# fsadm
fsadm: readlink does not support options -e -n
# fsadm --help
fsadm: readlink does not support options -e -n

# rpm -qf `which readlink`
coreutils-5.2.1-31.7

#rpm -qf `which fsadm`
lvm2-2.02.35-1.el4

Comment 1 Milan Broz 2008-04-27 18:00:00 UTC
eh, missing ...not sure if update of coreutils in 4.7 helps :-)


Comment 6 Zdenek Kabelac 2008-04-29 15:26:47 UTC
Fixed upstream in CVS 
scripts/fsadm.sh version 1.6
tools/lvresize.c version 1.97

Comment 9 Corey Marthaler 2008-06-30 16:11:06 UTC
Fix verified in lvm2-2.02.37-3.el4.

Comment 11 errata-xmlrpc 2008-07-24 20:08:08 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0776.html


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