Bug 761797 (GLUSTER-65)

Summary: Some SQLite operations as performed by Firefox fail
Product: [Community] GlusterFS Reporter: Basavanagowda Kanur <gowda>
Component: coreAssignee: Pavan Vilas Sondur <pavan>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: anush, gluster-bugs, hauser, pavan, shehjart
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: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Basavanagowda Kanur 2009-06-25 06:45:59 UTC
[Migrated from savannah BTS] - bug 26271 [https://savannah.nongnu.org/bugs/?26271]

Tue 21 Apr 2009 04:41:22 PM GMT, original submission:

This is particularly obvious when it comes to saving bookmarks when /home is mounted on GlusterFS. To reproduce:

mount /home on AFR/Replicate GlusterFS cluster with 2 nodes with both nodes up. Fire up X and Firefox. Add a bookmark and exit Firefox. Restart firefox and check the bookmark list on the menu - the bookmark that was added won't appear in the list.

This problem also exhibits in other Firefox databases (saving website login credentials, for example), but the bookmark test is the easiest, quickest and most reliable to reproduce.

--------------------------------------------------------------------------------
Thu 14 May 2009 11:11:27 PM GMT, comment #1 by 	Amar Tumballi <amarts>:

Hi Gordan,
With the 2.0.1 release, I couldn't reproduce this behavior with the following volume file.

---
volume posix1
type storage/posix
option directory /tmp/test-home1
end-volume

volume locks1
type features/locks
subvolumes posix1
end-volume

volume posix2
type storage/posix
option directory /tmp/test-home2
end-volume

volume locks2
type features/locks
subvolumes posix2
end-volume

volume server1
type protocol/server
option listen-port 7001
option auth.addr.locks1.allow *
subvolumes locks1
end-volume

volume server2
type protocol/server
option listen-port 7002
option auth.addr.locks2.allow *
subvolumes locks2
end-volume

volume client1
type protocol/client
option remote-host localhost
option remote-port 7001
option remote-subvolume locks1
end-volume

volume client2
type protocol/client
option remote-host localhost
option remote-port 7002
option remote-subvolume locks2
end-volume

volume afr
type cluster/afr
subvolumes client1 client2
end-volume
-----------

Can you confirm this is the same behavior with this volume file in your setup? (Also can you check if the permission on /home is 0777 ?)

Comment 1 Shehjar Tikoo 2010-03-02 08:30:58 UTC

*** This bug has been marked as a duplicate of bug 6 ***