Bug 762344 (GLUSTER-612)

Summary: RPM query fails on a replicated rootfs
Product: [Community] GlusterFS Reporter: Harshavardhana <fharshav>
Component: replicateAssignee: Pavan Vilas Sondur <pavan>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: mainlineCC: cww, gluster-bugs, pavan, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
server1 volume
none
server2 volume
none
server3 volume none

Description Harshavardhana 2010-02-13 12:32:46 UTC
Created attachment 145 [details]
New xcdroast spec file (same as 0.96e-3 spec file patched)

Comment 1 Harshavardhana 2010-02-13 12:33:12 UTC
Created attachment 146 [details]
RPM patch to run post-uninst before post-inst

Comment 2 Harshavardhana 2010-02-13 12:33:30 UTC
Created attachment 147 [details]
add dependency on inetd, clean rpmsave rename, fix upgrade issues

Comment 3 Harshavardhana 2010-02-13 15:15:59 UTC
bash# rpm -ql binutils
rpmdb: Thread/process 14002/140059925202832 failed: Thread died in Berkeley DB library
error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 -  (-30974)
error: cannot open Packages database in /var/lib/rpm
rpmdb: Thread/process 14002/140059925202832 failed: Thread died in Berkeley DB library
error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages database in /var/lib/rpm
package binutils is not installed


Just on a posix + posix-locks export it never happens. 

ls -l /var/lib/rpm/
total 38176
-rw-r--r-- 1 root root  2686976 Feb 13 18:33 Basenames
-rw-r--r-- 1 root root    49152 Feb 13 18:33 Conflictname
-rw-r--r-- 1 root root  1064960 Feb 13 18:33 Dirnames
-rw-r--r-- 1 root root  5292032 Feb 13 18:33 Filedigests
-rw-r--r-- 1 root root    49152 Feb 13 18:33 Group
-rw-r--r-- 1 root root    49152 Feb 13 18:33 Installtid
-rw-r--r-- 1 root root    49152 Feb 13 18:33 Name
-rw-r--r-- 1 root root    49152 Feb 13 18:33 Obsoletename
-rw-r--r-- 1 root root 28033024 Feb 13 18:33 Packages
-rw-r--r-- 1 root root   376832 Feb 13 18:33 Providename
-rw-r--r-- 1 root root   114688 Feb 13 18:33 Provideversion
-rw-r--r-- 1 root root    12288 Dec  8 07:59 Pubkeys
-rw-r--r-- 1 root root   245760 Feb 13 18:33 Requirename
-rw-r--r-- 1 root root   212992 Feb 13 18:33 Requireversion
-rw-r--r-- 1 root root    98304 Feb 13 18:33 Sha1header
-rw-r--r-- 1 root root    49152 Feb 13 18:33 Sigmd5
-rw-r--r-- 1 root root    49152 Feb 13 18:33 Triggername
-rw-r--r-- 1 root root        0 Feb 13 18:16 __db.000
-rw-r--r-- 1 root root    24576 Feb 13 20:37 __db.001
-rw-r--r-- 1 root root   229376 Feb 13 20:37 __db.002
-rw-r--r-- 1 root root  1318912 Feb 13 20:37 __db.003
-rw-r--r-- 1 root root   753664 Feb 13 20:33 __db.004

Comment 4 Pavan Vilas Sondur 2010-08-10 06:29:22 UTC
Internal bug on unsupported configuration (server side replication). Closing for now.