Re: [Gluster-users] sharding in glusterfs

[Pranith Kumar Karampuri]

On Mon, Sep 17, 2018 at 4:14 AM Ashayam Gupta 
wrote:

> Hi All,
>
> We are currently using glusterfs for storing large files with write-once
> and multiple concurrent reads, and were interested in understanding one of
> the features of glusterfs called sharding for our use case.
>
> So far from the talk given by the developer [
> https://www.youtube.com/watch?v=aAlLy9k65Gw] and the git issue [
> https://github.com/gluster/glusterfs/issues/290] , we know that it was
> developed for large VM images as use case and the second link does talk
> about a more general purpose usage , but we are not clear if there are some
> issues if used for non-VM image large files [which is the use case for us].
>
> Therefore it would be helpful if we can have some pointers or more
> information about the more general use-case scenario for sharding and any
> shortcomings if any , in case we use it for our scenario which is non-VM
> large files with write-once and multiple concurrent reads.Also it would be
> very helpful if you can suggest the best approach/settings for our use case
> scenario.
>

Sharding is developed for Big file usecases and at the moment only supports
single writer workload. I also added the maintainers for sharding to the
thread. May be giving a bit of detail about access pattern w.r.t. number of
mounts that are used for writing/reading would be helpful. I am assuming
write-once and multiple concurrent reads means that Reads will not happen
until the file is completely written to. Could you explain  a bit more
about the workload?


>
> Thanks
> Ashayam Gupta
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users



-- 
Pranith
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Cannot connect using NFS, protocol problems

[Jiffin Tony Thottan]

On Monday 17 September 2018 11:53 PM, Arthur Pemberton wrote:
When I try to mount to my working glusterfs cluster using NFS, I can't 
establish the connection.


# mount -v -t nfs -o mountproto=tcp,proto=tcp,vers=3
SERVER:/VOLUME /mnt/glusterfs
mount.nfs: timeout set for Mon Sep 17 13:23:44 2018
mount.nfs: trying text-based options
'mountproto=tcp,proto=tcp,vers=3,addr=172.24.16.17'
mount.nfs: prog 13, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'mountproto=tcp,proto=tcp,vers=3,addr=172.24.16.17'
mount.nfs: prog 13, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: trying text-based options
'mountproto=tcp,proto=tcp,vers=3,addr=172.24.16.17'
mount.nfs: prog 13, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not
supported


This is on CentOS 7, I don't really know how to troubleshoot.




Are u sure the volume is exported via NFS, what showmount -e  
returns from the client


It is look like client was not able to connect the nfs server?



Regards,
Jiffin

Arthur Pemberton



___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users


___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gluster.org Blog - Call for Posts: Sept 11-30

[Sankarshan Mukhopadhyay]

On Mon, Sep 10, 2018 at 10:57 PM Amye Scavarda  wrote:
>
> We're putting out a call for posts for the Gluster.org blog over the next few 
> months. Within the gluster ecosystem, we have a social-me...@gluster.org list 
> to help highlight posts, whether that's something that's already posted 
> elsewhere on the web or something that should go on the main gluster.org blog.
>
> However, the social-media@ list has editors on it as well to help your 
> content get out there!
>
> What are we looking for?
>
> Gluster-related topics!
>
> Specifically, if you submitted an abstract for a conference and are still 
> interested in writing on that topic, this is a great place for you!
> This will also help with upcoming calls for papers, like DevConf.CZ/FOSDEM. 
> (October 26 for DevConf.cz, FOSDEM may have a Software Defined Storage 
> DevRoom)
>
> This can also include: case studies, problems you've run into with Gluster 
> and resolved, features you're working on that you'd like to describe in more 
> detail.
>

In recent times I've seen a few posts on -users around troubleshooting
of scenarios. I was wondering (if the participant is willing) about
doing small conversations/interviews around monitoring/troubleshooting
that these practitioners are undertaking. And as an extension to that
- whether "Gluster in containers" is a thing that we see users
adopting/deploying.

> Let me know if you have questions, this call for posts runs from September 
> 11th through September 30th. After that, I'll work with interested folks to 
> edit and publish to the gluster.org blog.
>
> Thanks!
> - amye
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Cannot connect using NFS, protocol problems

[Arthur Pemberton]

When I try to mount to my working glusterfs cluster using NFS, I can't
establish the connection.

# mount -v -t nfs -o mountproto=tcp,proto=tcp,vers=3 SERVER:/VOLUME
> /mnt/glusterfs
> mount.nfs: timeout set for Mon Sep 17 13:23:44 2018
> mount.nfs: trying text-based options
> 'mountproto=tcp,proto=tcp,vers=3,addr=172.24.16.17'
> mount.nfs: prog 13, trying vers=3, prot=6
> mount.nfs: portmap query failed: RPC: Program not registered
> mount.nfs: trying text-based options
> 'mountproto=tcp,proto=tcp,vers=3,addr=172.24.16.17'
> mount.nfs: prog 13, trying vers=3, prot=6
> mount.nfs: portmap query failed: RPC: Program not registered
> mount.nfs: trying text-based options
> 'mountproto=tcp,proto=tcp,vers=3,addr=172.24.16.17'
> mount.nfs: prog 13, trying vers=3, prot=6
> mount.nfs: portmap query failed: RPC: Program not registered
> mount.nfs: requested NFS version or transport protocol is not supported


This is on CentOS 7, I don't really know how to troubleshoot.

Arthur Pemberton
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] vfs_gluster broken

[Terry McGuire]

> On Sep 14, 2018, at 02:32, Anoop C S  wrote:
> 
> On Wed, 2018-09-12 at 10:37 -0600, Terry McGuire wrote:
>> 
 My gluster version initially was 3.10.12.  I’ve since updated to gluster 
 3.12.13, but the
 symptoms
 are the same.
 
> 
> Did you mean 3.10.12 or 3.12.12?(your initial GlusterFS version)?
> 
> If GlusterFS was at v3.10.12, are you sure that you were experiencing issues 
> with samba v4.7.1?

Definitely 3.10.12.  Our production service is still using it:

root@mfs-01 ~]#gluster --version
glusterfs 3.10.12


Definitely samba 4.7.1:

root@mfs-01 ~]#smbstatus --version
Version 4.7.1


As an experiment, I’ve now upgraded our test machines all the way to gluster 
4.1.4, but the symptoms are the same.


>> Actually, yes.  Large numbers of:
>> 
>> [2018/09/12 09:37:17.873711,  0] 
>> ../source3/modules/vfs_glusterfs.c:996(vfs_gluster_stat)
>>  glfs_stat(.) failed: Invalid argument
> 
> Might be related to https://bugzilla.samba.org/show_bug.cgi?id=13585.
> 
> Can you try installing a version of GlusterFS < 3.12.13 and see if it works 
> normally?

This bug does seem to fit the symptoms, however my prod service is already < 
3.12.3 and is not normal.

Perhaps my best option is to try downgrading samba to the original version and 
see if it restores proper function, until a patched version of Gluster is 
available.  Or just live with slow FUSE-backed SMB for the time being.

Terry

___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Failures during rebalance on gluster distributed disperse volume

[Mauro Tridici]

Hi Nithya,

thank you.
Rabalance terminated (with a lot of failures) a few days ago.
Due to some I/O errors during write operations on gluster volume, I had to 
re-launch fix-layout rebalance

Now, fix-layouts rebalance is completed and I can write data without I/O 
errors. 
As soon as possible I will start the upgrade procedure.

Thank you again for your support.
Regards,
Mauro

> Il giorno 16 set 2018, alle ore 06:07, Nithya Balachandran 
>  ha scritto:
> 
> Hi Mauro,
> 
> Please stop the rebalance before you upgrade.
> Thanks,
> Nithya
> 
> On 15 September 2018 at 22:55, Mauro Tridici  > wrote:
> 
> Hi Sunil,
> 
> many thanks to you too.
> I will follow your suggestions and the guide for upgrading to 3.12
> 
> Crossing fingers :-)
> Regards,
> Mauro
> 
>> Il giorno 15 set 2018, alle ore 11:57, Sunil Kumar Heggodu Gopala Acharya 
>> mailto:shegg...@redhat.com>> ha scritto:
>> 
>> Hi Mauro,
>> 
>> As Nithya highlighted FALLOCATE support for EC volumes went in 3.11 as part 
>> of https://bugzilla.redhat.com/show_bug.cgi?id=1454686 
>> . Hence, upgrading to 
>> 3.12 as suggested before would be a right move.
>> 
>> Here is the documentation for upgrading to 3.12: 
>> https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_3.12/ 
>> 
>> 
>> Regards,
>> SUNIL KUMAR ACHARYA
>> SENIOR SOFTWARE ENGINEER
>> Red Hat 
>> 
>>  
>> T: +91-8067935170    
>>  
>> 
>>   
>> TRIED. TESTED. TRUSTED. 
>> 
>> On Sat, Sep 15, 2018 at 3:42 AM, Mauro Tridici > > wrote:
>> 
>> Hi Nithya,
>> 
>> thank you very much for your answer.
>> I will wait for @Sunil opinion too before starting the upgrade procedure.
>> 
>> Since it will be the first upgrade of our Gluster cluster, I would like to 
>> know if it could be a “virtually dangerous" procedure and if it will be the 
>> risk of losing data :-) 
>> Unfortunately, I can’t do a preventive copy of the volume data in another 
>> location.
>> If it is possible, could you please illustrate the right steps needed to 
>> complete the upgrade procedure from the 3.10.5 to the 3.12 version?
>> 
>> Thank you again, Nithya.
>> Thank you to all of you for the help!
>> 
>> Regards,
>> Mauro
>> 
>>> Il giorno 14 set 2018, alle ore 16:59, Nithya Balachandran 
>>> mailto:nbala...@redhat.com>> ha scritto:
>>> 
>>> Hi Mauro,
>>> 
>>> 
>>> The rebalance code started using fallocate in 3.10.5 
>>> (https://bugzilla.redhat.com/show_bug.cgi?id=1473132 
>>> ) which works fine on 
>>> replicated volumes. However, we neglected to test this with EC volumes on 
>>> 3.10. Once we discovered the issue, the EC fallocate implementation was 
>>> made available in 3.11.
>>> 
>>> At this point, I'm afraid the only option I see is to upgrade to at least 
>>> 3.12.
>>> 
>>> @Sunil, do you have anything to add?
>>> 
>>> Regards,
>>> Nithya
>>> 
>>> On 13 September 2018 at 18:34, Mauro Tridici >> > wrote:
>>> 
>>> Hi Nithya,
>>> 
>>> thank you for involving EC group.
>>> I will wait for your suggestions.
>>> 
>>> Regards,
>>> Mauro
>>> 
 Il giorno 13 set 2018, alle ore 13:38, Nithya Balachandran 
 mailto:nbala...@redhat.com>> ha scritto:
 
 This looks like an issue because rebalance switched to using fallocate 
 which EC did not have implemented at that point.
 
 @Pranith, @Ashish, which version of gluster had support for fallocate in 
 EC?
 
 
 Regards,
 Nithya
 
 On 12 September 2018 at 19:24, Mauro Tridici >>> > wrote:
 Dear All,
 
 I recently added 3 servers (each one with 12 bricks) to an existing 
 Gluster Distributed Disperse Volume.
 Volume extension has been completed without error and I already executed 
 the rebalance procedure with fix-layout option with no problem.
 I just launched the rebalance procedure without fix-layout option, but, as 
 you can see in the output below, I noticed that some failures have been 
 detected.
 
 [root@s01 glusterfs]# gluster v rebalance tier2 status
 Node Rebalanced-files  size
scanned  failures   skipped   status  run time in 
 h:m:s
-  ---   ---   
 ---   ---   ---  
 --
localhost71176 3.2MB
2137557   1530391  8128  in progress   13:59:05
  s02-stg00Bytes
  0 0   

Re: [Gluster-users] Geo-replication keeps failing.

[Sunny Kumar]

Hi Alvin,

Please share complete log and also master mount log.
 - Sunny
On Thu, Sep 13, 2018 at 5:07 PM Alvin Starr  wrote:
>
> We are running glusterfs-3.8.9-1.el7.x86_64 with geo-replication.
>
> I have been having ongoing problems with the replication failing after
> some time.
>
> Once it has failed restarting it results in the attached logfile snippet.
>
>
> --
> Alvin Starr   ||   land:  (905)513-7688
> Netvel Inc.   ||   Cell:  (416)806-0133
> al...@netvel.net  ||
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users