[Gluster-users] 2.0.0rc7 bug

Kirby Zhou kirbyzhou at sohu-rd.com
Thu Mar 26 10:01:22 UTC 2009

Cannot remove invalid symbol link


[root at xen-727057 XXX]# ln -s ../logX.txt .                            #
../logX.txt is not exist!!

[root at xen-727057 XXX]# ll

total 0

lrwxrwxrwx 1 nobody nobody 11 Mar 26 17:59 logX.txt -> ../logX.txt

[root at xen-727057 XXX]# rm logX.txt 

rm: remove symbolic link `logX.txt'? y

rm: cannot remove `logX.txt': No such file or directory


From: harshavardhanacool at gmail.com [mailto:harshavardhanacool at gmail.com] On
Behalf Of Harshavardhana
Sent: Thursday, March 26, 2009 1:17 PM
To: Kirby Zhou
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] 2.0.0rc7 rpmbuild failed


Hi Kirby,

     For the time being if you don't require mod_glusterfs you can build
     without mod_glusterfs by passing the following commands in rpmbuild 

     "rpmbuild -ta glusterfs-2.0.0rc7.tar.gz --without modglfs"

     Issue reported by you is not reproducible on our test cluster with
CentOS 5.2 
     and apache 2.2.10 version. Can you please state your distribution and
     where you are actually trying to build rpms for glusterfs?

"Yantra Shilpi"
Z Research Inc - http://www.zresearch.com

On Thu, Mar 26, 2009 at 8:38 AM, Kirby Zhou <kirbyzhou at sohu-rd.com> wrote:

+ /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
* WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
*          to fail. To ignore these errors, you can set the '$QA_RPATHS'
*          environment variable which is a bitmask allowing the values
*          below. The current value of QA_RPATHS is 0x0000.
*    0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
*               issue but are introducing redundant searchpaths without
*               providing a benefit. They can also cause errors in multilib
*               environments.
*    0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
*               nor relative filenames and can therefore be a SECURITY risk
*    0x0004 ... insecure RPATHs; these are relative RPATHs which are a
*               SECURITY risk
*    0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
*               RPATHs; this is just a minor issue but usually unwanted
*    0x0010 ... the RPATH is empty; there is no reason for such RPATHs
*               and they cause unneeded work while loading libraries
*    0x0020 ... an RPATH references '..' of an absolute path; this will
*               the functionality when the path before '..' is a symlink
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
*   $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths
*   $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
ERROR   0002: file
'/usr/lib64/glusterfs/2.0.0rc7/apache/2.2/mod_glusterfs.so' contains an
invalid rpath
'/root/rpmbuild/BUILD/glusterfs-2.0.0rc7/libglusterfsclient/src/.libs' in
error: Bad exit status from /var/tmp/rpm-tmp.14389 (%install)

Gluster-users mailing list
Gluster-users at gluster.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090326/7f1710d5/attachment.html>

More information about the Gluster-users mailing list