Re: [Gluster-users] [Gluster-devel] Request for Comments: Upgrades from 3.x to 4.0+

2017-11-05 Thread Kaushal M 
On Fri, Nov 3, 2017 at 8:50 PM, Alastair Neil  wrote:
> Just so I am clear the upgrade process will be as follows:
>
> upgrade all clients to 4.0
>
> rolling upgrade all servers to 4.0 (with GD1)
>
> kill all GD1 daemons on all servers and run upgrade script (new clients
> unable to connect at this point)
>
> start GD2 ( necessary or does the upgrade script do this?)
>
>
> I assume that once the cluster had been migrated to GD2 the glusterd startup
> script will be smart enough to start the correct version?
>

This should be the process, mostly.

The upgrade script needs to GD2 running on all nodes before it can
begin migration.
But they don't need to have a cluster formed, the script should take
care of forming the cluster.


> -Thanks
>
>
>
>
>
> On 3 November 2017 at 04:06, Kaushal M  wrote:
>>
>> On Thu, Nov 2, 2017 at 7:53 PM, Darrell Budic 
>> wrote:
>> > Will the various client packages (centos in my case) be able to
>> > automatically handle the upgrade vs new install decision, or will we be
>> > required to do something manually to determine that?
>>
>> We should be able to do this with CentOS (and other RPM based distros)
>> which have well split glusterfs packages currently.
>> At this moment, I don't know exactly how much can be handled
>> automatically, but I expect the amount of manual intervention to be
>> minimal.
>> The least minimum amount of manual work needed would be enabling and
>> starting GD2 and starting the migration script.
>>
>> >
>> > It’s a little unclear that things will continue without interruption
>> > because
>> > of the way you describe the change from GD1 to GD2, since it sounds like
>> > it
>> > stops GD1.
>>
>> With the described upgrade strategy, we can ensure continuous volume
>> access to clients during the whole process (provided volumes have been
>> setup with replication or ec).
>>
>> During the migration from GD1 to GD2, any existing clients still
>> retain access, and can continue to work without interruption.
>> This is possible because gluster keeps the management  (glusterds) and
>> data (bricks and clients) parts separate.
>> So it is possible to interrupt the management parts, without
>> interrupting data access to existing clients.
>> Clients and the server side brick processes need GlusterD to start up.
>> But once they're running, they can run without GlusterD. GlusterD is
>> only required again if something goes wrong.
>> Stopping GD1 during the migration process, will not lead to any
>> interruptions for existing clients.
>> The brick process continue to run, and any connected clients continue
>> to remain connected to the bricks.
>> Any new clients which try to mount the volumes during this migration
>> will fail, as a GlusterD will not be available (either GD1 or GD2).
>>
>> > Early days, obviously, but if you could clarify if that’s what
>> > we’re used to as a rolling upgrade or how it works, that would be
>> > appreciated.
>>
>> A Gluster rolling upgrade process, allows data access to volumes
>> during the process, while upgrading the brick processes as well.
>> Rolling upgrades with uninterrupted access requires that volumes have
>> redundancy (replicate or ec).
>> Rolling upgrades involves upgrading servers belonging to a redundancy
>> set (replica set or ec set), one at a time.
>> One at a time,
>> - A server is picked from a redundancy set
>> - All Gluster processes are killed on the server, glusterd, bricks and
>> other daemons included.
>> - Gluster is upgraded and restarted on the server
>> - A heal is performed to heal new data onto the bricks.
>> - Move onto next server after heal finishes.
>>
>> Clients maintain uninterrupted access, because a full redundancy set
>> is never taken offline all at once.
>>
>> > Also clarification that we’ll be able to upgrade from 3.x
>> > (3.1x?) to 4.0, manually or automatically?
>>
>> Rolling upgrades from 3.1x to 4.0 are a manual process. But I believe,
>> gdeploy has playbooks to automate it.
>> At the end of this you will be left with a 4.0 cluster, but still be
>> running GD1.
>> Upgrading from GD1 to GD2, in 4.0 will be a manual process. A script
>> that automates this is planned only for 4.1.
>>
>> >
>> >
>> > 
>> > From: Kaushal M 
>> > Subject: [Gluster-users] Request for Comments: Upgrades from 3.x to 4.0+
>> > Date: November 2, 2017 at 3:56:05 AM CDT
>> > To: gluster-users@gluster.org; Gluster Devel
>> >
>> > We're fast approaching the time for Gluster-4.0. And we would like to
>> > set out the expected upgrade strategy and try to polish it to be as
>> > user friendly as possible.
>> >
>> > We're getting this out here now, because there was quite a bit of
>> > concern and confusion regarding the upgrades between 3.x and 4.0+.
>> >
>> > ---
>> > ## Background
>> >
>> > Gluster-4.0 will bring a newer management daemon, GlusterD-2.0 (GD2),
>> > which is backwards

Re: [Gluster-users] Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.

2017-11-05 Thread Laura Bailey 
Do the users have permission to see/interact with the directories, in
addition to the files?

On Mon, Nov 6, 2017 at 1:55 PM, Nithya Balachandran 
wrote:

> Hi,
>
> Please provide the gluster volume info. Do you see any errors in the
> client mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)?
>
>
> Thanks,
> Nithya
>
> On 6 November 2017 at 05:13, Sam McLeod  wrote:
>
>> We've got an issue with Gluster (3.12.x) where clients can't see
>> directories that exist or are created within a mounted volume.
>>
>>
>> We can see files, but not directories (with ls, find etc...)
>> We can enter (cd) into directories, even if we can't see them.
>>
>> - Host typology is: 2 replica, 1 arbiter.
>> - Volumes are: replicated and running on XFS on the hosts.
>> - Clients are: GlusterFS native fuse client (mount.glusterfs), the same
>> version and op-version as the hosts.
>> - Gluster server and client version: 3.12.2 (also found on 3.12.1, unsure
>> about previous versions) running on CentOS 7.
>>
>>
>> Examples:
>>
>>
>> mount:
>> 192.168.0.151:/gluster_vol on /var/lib/mountedgluster type
>> fuse.glusterfs (rw,relatime,user_id=0,group_i
>> d=0,default_permissions,allow_other,max_read=131072)
>>
>> root@gluster-client:/var/lib/mountedgluster  # ls -la
>> total 0
>>
>> (note no . or .. directories)
>>
>> root@gluster-client:/var/lib/mountedgluster  # touch test
>> root@gluster-client:/var/lib/mountedgluster  # ls -la
>> total 0
>> -rw-r--r--. 1 root root 0 Nov  6 10:10 test
>>
>> ("test" file shows up. Still no . or .. directories.)
>>
>> root@gluster-client:/var/lib/mountedgluster  # mkdir testdir
>> root@gluster-client:/var/lib/mountedgluster  # ls -la
>> total 0
>> -rw-r--r--. 1 root root 0 Nov  6 10:10 test
>>
>> (directory was made, but doesn't show in ls)
>>
>> root@gluster-client:/var/lib/mountedgluster  # cd testdir
>> root@gluster-client:/var/lib/mountedgluster/testdir  # ls -la
>> total 0
>>
>> (cd works, no . or .. shown in ls though)
>>
>> root@gluster-client:/var/lib/mountedgluster/testdir  # touch test
>> root@gluster-client:/var/lib/mountedgluster/testdir  # ls -la
>> total 0
>> -rw-r--r--. 1 root root 0 Nov  6 10:10 test
>>
>> (can create test file in testdir)
>>
>>
>> root@gluster-client:/var/lib/mountedgluster/testdir  # cd ..
>> root@gluster-client:/var/lib/mountedgluster  # ls -ld testdir
>> drwxr-xr-x. 2 root root 4096 Nov  6 10:10 testdir
>>
>> (going back to parent directory, although ls -la doesn't show the
>> directory, if I specify the name to ls -ld it does show)
>>
>>
>>
>> --
>> Sam McLeod
>> https://twitter.com/s_mcleod
>> https://smcleod.net
>>
>>
>> ___
>> Gluster-users mailing list
>> Gluster-users@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>



-- 
Laura Bailey
Senior Technical Writer
Customer Content Services BNE
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.

2017-11-05 Thread Nithya Balachandran 
Hi,

Please provide the gluster volume info. Do you see any errors in the client
mount log file (/var/log/glusterfs/var-lib-mountedgluster.log)?


Thanks,
Nithya

On 6 November 2017 at 05:13, Sam McLeod  wrote:

> We've got an issue with Gluster (3.12.x) where clients can't see
> directories that exist or are created within a mounted volume.
>
>
> We can see files, but not directories (with ls, find etc...)
> We can enter (cd) into directories, even if we can't see them.
>
> - Host typology is: 2 replica, 1 arbiter.
> - Volumes are: replicated and running on XFS on the hosts.
> - Clients are: GlusterFS native fuse client (mount.glusterfs), the same
> version and op-version as the hosts.
> - Gluster server and client version: 3.12.2 (also found on 3.12.1, unsure
> about previous versions) running on CentOS 7.
>
>
> Examples:
>
>
> mount:
> 192.168.0.151:/gluster_vol on /var/lib/mountedgluster type fuse.glusterfs
> (rw,relatime,user_id=0,group_id=0,default_permissions,
> allow_other,max_read=131072)
>
> root@gluster-client:/var/lib/mountedgluster  # ls -la
> total 0
>
> (note no . or .. directories)
>
> root@gluster-client:/var/lib/mountedgluster  # touch test
> root@gluster-client:/var/lib/mountedgluster  # ls -la
> total 0
> -rw-r--r--. 1 root root 0 Nov  6 10:10 test
>
> ("test" file shows up. Still no . or .. directories.)
>
> root@gluster-client:/var/lib/mountedgluster  # mkdir testdir
> root@gluster-client:/var/lib/mountedgluster  # ls -la
> total 0
> -rw-r--r--. 1 root root 0 Nov  6 10:10 test
>
> (directory was made, but doesn't show in ls)
>
> root@gluster-client:/var/lib/mountedgluster  # cd testdir
> root@gluster-client:/var/lib/mountedgluster/testdir  # ls -la
> total 0
>
> (cd works, no . or .. shown in ls though)
>
> root@gluster-client:/var/lib/mountedgluster/testdir  # touch test
> root@gluster-client:/var/lib/mountedgluster/testdir  # ls -la
> total 0
> -rw-r--r--. 1 root root 0 Nov  6 10:10 test
>
> (can create test file in testdir)
>
>
> root@gluster-client:/var/lib/mountedgluster/testdir  # cd ..
> root@gluster-client:/var/lib/mountedgluster  # ls -ld testdir
> drwxr-xr-x. 2 root root 4096 Nov  6 10:10 testdir
>
> (going back to parent directory, although ls -la doesn't show the
> directory, if I specify the name to ls -ld it does show)
>
>
>
> --
> Sam McLeod
> https://twitter.com/s_mcleod
> https://smcleod.net
>
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Gluster clients can't see directories that exist or are created within a mounted volume, but can enter them.

2017-11-05 Thread Sam McLeod 
We've got an issue with Gluster (3.12.x) where clients can't see directories 
that exist or are created within a mounted volume.


We can see files, but not directories (with ls, find etc...)
We can enter (cd) into directories, even if we can't see them.

- Host typology is: 2 replica, 1 arbiter.
- Volumes are: replicated and running on XFS on the hosts.
- Clients are: GlusterFS native fuse client (mount.glusterfs), the same version 
and op-version as the hosts.
- Gluster server and client version: 3.12.2 (also found on 3.12.1, unsure about 
previous versions) running on CentOS 7.


Examples:


mount:
192.168.0.151:/gluster_vol on /var/lib/mountedgluster type fuse.glusterfs 
(rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
 
root@gluster-client:/var/lib/mountedgluster  # ls -la
total 0
 
(note no . or .. directories)
 
root@gluster-client:/var/lib/mountedgluster  # touch test
root@gluster-client:/var/lib/mountedgluster  # ls -la
total 0
-rw-r--r--. 1 root root 0 Nov  6 10:10 test
 
("test" file shows up. Still no . or .. directories.)
 
root@gluster-client:/var/lib/mountedgluster  # mkdir testdir
root@gluster-client:/var/lib/mountedgluster  # ls -la
total 0
-rw-r--r--. 1 root root 0 Nov  6 10:10 test
 
(directory was made, but doesn't show in ls)
 
root@gluster-client:/var/lib/mountedgluster  # cd testdir
root@gluster-client:/var/lib/mountedgluster/testdir  # ls -la
total 0
 
(cd works, no . or .. shown in ls though)
 
root@gluster-client:/var/lib/mountedgluster/testdir  # touch test
root@gluster-client:/var/lib/mountedgluster/testdir  # ls -la
total 0
-rw-r--r--. 1 root root 0 Nov  6 10:10 test
 
(can create test file in testdir)
 
 
root@gluster-client:/var/lib/mountedgluster/testdir  # cd ..
root@gluster-client:/var/lib/mountedgluster  # ls -ld testdir
drwxr-xr-x. 2 root root 4096 Nov  6 10:10 testdir
 
(going back to parent directory, although ls -la doesn't show the directory, if 
I specify the name to ls -ld it does show)
 
 

--
Sam McLeod 
https://twitter.com/s_mcleod
https://smcleod.net

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