Re: Xattr Metadata - Mandatory?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Actually, scratch that - the replication isn't working properly - it doesn't seem to be working at all when node3 is already up and running and node2 comes up and joins the cluster. I can create and write a file in /home/gordan after mounthing these volumes files under /home on each node and the files don't end up replicating in either direction. No metadata gets created, either.

Volume spec files on the two nodes are attached.

Nothing appears in the logs except the usual messages that the connections from the other node were connected.

This is with latest 2.0.1.

Gordan

Gordan Bobic wrote:
No, no such options are set in my volume spec file.

Gordan

Raghavendra G wrote:
Hi,

have you disabled changelog in afr? following are the options corresponding to changelog.

option data-change-log off
option metadata-change-log off
option entry-change-log off

regards,
On Tue, May 26, 2009 at 2:26 AM, Gordan Bobic <gordan@xxxxxxxxxx <mailto:gordan@xxxxxxxxxx>> wrote:

    Is metadata mandatory on all files under AFR? The reason I ask is
    because I seem to have a lot of files in my replicated directories
    that don't have the said metadata. This includes newly created files
    that seem to replicated between the nodes correctly. Is this normal?
    Nothing appears in the logs when creating these metadataless files.

    Gordan


    _______________________________________________
    Gluster-devel mailing list
    Gluster-devel@xxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxx>
    http://lists.nongnu.org/mailman/listinfo/gluster-devel




--
Raghavendra G




volume home3
	type protocol/client
	option transport-type socket
	option transport.address-family inet
	option remote-host 10.2.0.10
	option remote-port 6997
	option remote-subvolume home3
end-volume

volume home-store
	type storage/posix
	option directory /gluster/home
end-volume

volume home2
	type features/posix-locks
	subvolumes home-store
end-volume

volume server
	type protocol/server
	option transport-type socket
	option transport.address-family inet
	option transport.socket.listen-port 6997
	subvolumes home2
	option auth.addr.home2.allow 127.0.0.1,10.2.*
end-volume

volume home
	type cluster/replicate
	subvolumes home2 home3
	option read-subvolume home2
	option favorite-child home2
end-volume
volume home2
	type protocol/client
	option transport-type socket
	option transport.address-family inet
	option remote-host 10.2.3.1
	option remote-port 6997
	option remote-subvolume home2
end-volume

volume home-store
	type storage/posix
	option directory /gluster/home
end-volume

volume home3
	type features/posix-locks
	subvolumes home-store
end-volume

volume server
	type protocol/server
	option transport-type socket
	option transport.address-family inet
	option transport.socket.listen-port 6997
	subvolumes home3
	option auth.addr.home3.allow 127.0.0.1,10.2.*
end-volume

volume home
	type cluster/replicate
	subvolumes home2 home3
	option read-subvolume home3
	option favorite-child home2
end-volume


[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux