[Gluster-devel] Netbsd regrsssion needs review

2015-01-19 Thread Emmanuel Dreyfus
Hi

NetBSD regression tests suffers a few spurious failures. I have fixes
for the two worst offenders:
http://review.gluster.org/9461
http://review.gluster.org/9074

Can someone please review?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


Re: [Gluster-devel] Unable to start samba service (smb) - due to /run/samba/ncalrpc - No such file or directory

2015-01-19 Thread Ira Cooper
Was this ever solved?

-Ira

- Original Message -
> Hi,
> 
> Can you post the output of #strace smbd and the logs(log.smbd)
> Was it an upgrade from older samba version? If yes, try clearing the
> /var/lib/samba/*.tdb files.
> 
> Regards,
> Poornima
> 
> 
> 
> 
> From: "Omkar Sharma" 
> To: gluster-devel@gluster.org
> Sent: Thursday, December 25, 2014 3:17:44 PM
> Subject: [Gluster-devel] Unable to start samba service (smb) - due to
> /run/samba/ncalrpc - No such file or directory
> 
> Hi,
> 
> I have installed samba-4.1.11-2.el6.x86_64.rpm and its dependencies taken
> from the below link:
> 
> http://download.gluster.org/pub/gluster/glusterfs/samba/CentOS/epel-6.5/x86_64/
> 
> The samba package got installed but unable to start the smb service. And I
> have smb file inside /etc/init.d/ directory.
> 
> $ sudo service smb status ...not showing any output
> $ sudo service smb start ...not showing any output
> 
> $ sudo /etc/init.d/smb status ...not showing any output
> $ sudo /etc/init.d/smb start ...not showing any output
> 
> And I went to see the log files inside /var/log/samba/.
> 
> $ vi /var/log/samba/log.smbd
> 
> smbd version 4.1.11 started.
> Copyright Andrew Tridgell and the Samba Team 1992-2013
> [2014/12/24 06:36:44.225371, 0] ../source3/smbd/server.c:1289(main)
> standard input is not a socket, assuming -D option
> [2014/12/24 06:36:44.472002, 0]
> ../lib/util/util.c:216(directory_create_or_exist)
> mkdir failed on directory /run/samba/ncalrpc: No such file or directory
> [2014/12/24 06:36:44.472317, 0] ../source3/smbd/server.c:1471(main)
> Failed to create pipe directory /run/samba/ncalrpc - No such file or
> directory
> 
> Why the samba rpm is not creating /run/samba directory and place the file
> ncalrpc ?
> 
> 
> With Regards,
> Omkar MN
> 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 
> 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel



[Gluster-devel] Ability to turn off 'glusterfs' protocol

2015-01-19 Thread Deepak Shetty
Hi All,
  I had opened this feature request sometime back
http://www.gluster.org/community/documentation/index.php/Features/turn-off-glusterfs-proto-access

I wanted to know what would be the right way to implement this ?

The goal here is to have a volume set option to turn off glusterfs/fuse
protocol access
just like how we have it today for NFS ( volume set nfs.export-volumes off)

1) Does GETSPEC allow passing the protocol being requested at mount, so
that glusterd can return success/failure and mount.gluster can error
accoridngly ?

2) Another way is to introduce another handshake after GETSPEC is
successfull, where client can request permission to mount using the said
protocol and glusterd returns success/failure based on the volume set
option being set or unset ?

Thoughts ?

thanx,
deepak
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


[Gluster-devel] Handling Georeplication rsync/tar+ssh failures more accurately.

2015-01-19 Thread Aravinda

Handling Geo-replication rsync/tar+ssh failures more accurately.


Existing:
-
1. Multiple Changelogs processed together, contents are segregated into 
ENTRY, META and DATA.
2. All Entry and Meta operations are sent to Slave gsyncd via RPC. Entry 
and Meta Ops are not parallel, executed in Slave sequentially.
3. For Data operations, GFIDs are queued and multiple rsync jobs(default 
is 3) sync data parallelly. (Since all entry available with previous 
step). These rsync jobs do not have any idea about to which changelog a 
GFID belong to.


If rsync/tar+ssh fails to sync then it retries all the steps mentioned 
above, after MAX retries it adds whole changelog(s) to Skipped 
List(since it is partially processed).


Problems:
-
No clue about Entry Ops failures in log/status
For rsync failures, all the steps are repeated even though not necessary.
Skips entire changelog even if one GFID has issue.
No way to get accurate list of failed GFIDs/files.


Planned enhancements:
-
- Log Entry Ops failures in log in following format and show in Status 
output.(separate log file, say 
/var/log/glusterfs/geo-replication/__/failures) 
(Log format: GFID|Changelog|Reason|Details)


   For example, 0d5fd80f-e5b5-4a9a-9023-879d730c9b82|1421648492|File 
exists with different GFID|E 57bad16c-222c-4c5e-80a8-87f77ffc9284 CREATE 
33188 0 0 ----0001/f1


- Make sure to remove the GFID from DATA list, if any Unlink captured in 
Changelog for which DATA is also recorded. This avoids rsync failure for 
these GFID's(rsync will fail because source file is Unlinked)


- Create a Unique list of GFIDs for rsync. (rsync will get benefited, 
avoids sending duplicate list to rsync)


- When Rsync fails, do not repeat steps 1 and 2, Retry only step 3.
1. FIRST RETRY: Stat in Master mount, rsync only for valid stat GFIDs.
2. SECOND RETRY: Retry first GFID separately and rest of them all 
at once, If First GFID fails add to skip list.
   If rest of the batch fails again, then do the same thing again. 
(Rsync first in the batch separately and rsync for rest of the batch)
   Repeat this step till all GFIDs get processed.(Either in skipped 
list or Success)


SECOND RETRY approach may affect geo-rep performance, but only when 
their is rsync problem.


If any failures, log in Failures log and show the number in the Status 
output.(Ex: b340deb7-8dd2-4d10-ab26-80acd3ff4954|1421648492|I/O Error|rsync)


Let me know your thoughts. Thanks

--
regards
Aravinda
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel