search for: posix_mkdir

...utage : gl-master-02, brick1-mvol1.log : [2017-06-23 17:48:30.093526] E [MSGID: 113018] [posix.c:2766:posix_create] 0-mvol1-posix: pre-operation lstat on parent /brick1/mvol1/.trashcan//2290/uploads failed [No such file or directory] [2017-06-23 17:48:30.093591] E [MSGID: 113018] [posix.c:1447:posix_mkdir] 0-mvol1-posix: pre-operation lstat on parent /brick1/mvol1/.trashcan//2290 failed [No such file or directory] [2017-06-23 17:48:30.093636] E [MSGID: 113027] [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of /brick1/mvol1/ failed [File exists] [2017-06-23 17:48:30.093670] E [MSGID: 113027] [po...

...mvol1.log : > > [2017-06-23 17:48:30.093526] E [MSGID: 113018]? > [posix.c:2766:posix_create] 0-mvol1-posix: pre-operation lstat on parent? > /brick1/mvol1/.trashcan//2290/uploads failed [No such file or directory] > [2017-06-23 17:48:30.093591] E [MSGID: 113018]? > [posix.c:1447:posix_mkdir] 0-mvol1-posix: pre-operation lstat on parent? > /brick1/mvol1/.trashcan//2290 failed [No such file or directory] > [2017-06-23 17:48:30.093636] E [MSGID: 113027]? > [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of /brick1/mvol1/ failed? > [File exists] > [2017-06-23 17:48:30.09367...

...>> [2017-06-23 17:48:30.093526] E [MSGID: 113018] >> [posix.c:2766:posix_create] 0-mvol1-posix: pre-operation lstat on parent >> /brick1/mvol1/.trashcan//2290/uploads failed [No such file or directory] >> [2017-06-23 17:48:30.093591] E [MSGID: 113018] >> [posix.c:1447:posix_mkdir] 0-mvol1-posix: pre-operation lstat on parent >> /brick1/mvol1/.trashcan//2290 failed [No such file or directory] >> [2017-06-23 17:48:30.093636] E [MSGID: 113027] >> [posix.c:1538:posix_mkdir] 0-mvol1-posix: mkdir of /brick1/mvol1/ failed >> [File exists] >> [2017-06-...

...(stat, cat, etc...) the filesystem reports that the file/directory does not exist, even though it does. When we try to create the file/directory we receive the following error which is also logged in /var/log/glusterfs/bricks/$brick.log: [2018-04-10 12:51:26.755928] E [MSGID: 113027] [posix.c:1779:posix_mkdir] 0-www-posix: mkdir of /storage/gluster/path/to/dir failed [File exists] We don't see this issue on all of the servers, but only on the servers that did not create the file/directory (so 2 of the 3 gluster nodes). We found that this issue does not resolve itself automatically. However, when w...

...filesystem reports that the file/directory does not exist, > even though it does. When we try to create the file/directory we receive > the following error which is also logged in > /var/log/glusterfs/bricks/$brick.log: > > [2018-04-10 12:51:26.755928] E [MSGID: 113027] [posix.c:1779:posix_mkdir] > 0-www-posix: mkdir of /storage/gluster/path/to/dir failed [File exists] > > We don't see this issue on all of the servers, but only on the servers that > did not create the file/directory (so 2 of the 3 gluster nodes). > > We found that this issue does not resolve itself au...

...ile/directory does not >> exist, >> even though it does. When we try to create the file/directory we receive >> the following error which is also logged in >> /var/log/glusterfs/bricks/$brick.log: >> >> [2018-04-10 12:51:26.755928] E [MSGID: 113027] [posix.c:1779:posix_mkdir] >> 0-www-posix: mkdir of /storage/gluster/path/to/dir failed [File exists] >> >> We don't see this issue on all of the servers, but only on the servers >> that >> did not create the file/directory (so 2 of the 3 gluster nodes). >> >> We found that this...

---------- Forwarded message ---------- From: Jose Sanchez <josesanc at carc.unm.edu> Date: 11 January 2018 at 22:05 Subject: Re: [Gluster-users] Creating cluster replica on 2 nodes 2 bricks each. To: Nithya Balachandran <nbalacha at redhat.com> Cc: gluster-users <gluster-users at gluster.org> Hi Nithya Thanks for helping me with this, I understand now , but I have few

Hi Nithya Thanks for helping me with this, I understand now , but I have few questions. When i had it setup in replica (just 2 nodes with 2 bricks) and tried to added , it failed. > [root at gluster01 ~]# gluster volume add-brick scratch replica 2 gluster01ib:/gdata/brick2/scratch gluster02ib:/gdata/brick2/scratch > volume add-brick: failed: /gdata/brick2/scratch is already part of a

...ensions are not required for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result some commands are not available, e.g. posix_encrypt, posix_open, posix_mkdir, posix_rmdir, posix_unlink, posix_whoami, getfacl and symlink. Using "-mNT1" reenabled them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still possible to connect to SMB1-only servers by default. N...

...ensions are not required for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result some commands are not available, e.g. posix_encrypt, posix_open, posix_mkdir, posix_rmdir, posix_unlink, posix_whoami, getfacl and symlink. Using "-mNT1" reenabled them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still possible to connect to SMB1-only servers by default. N...

...ensions are not required for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result some commands are not available, e.g. posix_encrypt, posix_open, posix_mkdir, posix_rmdir, posix_unlink, posix_whoami, getfacl and symlink. Using "-mNT1" reenabled them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still possible to connect to SMB1-only servers by default. N...

...ensions are not required for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result some commands are not available, e.g. posix_encrypt, posix_open, posix_mkdir, posix_rmdir, posix_unlink, posix_whoami, getfacl and symlink. Using "-mNT1" reenabled them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still possible to connect to SMB1-only servers by default. sm...

...ensions are not required for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result some commands are not available, e.g. posix_encrypt, posix_open, posix_mkdir, posix_rmdir, posix_unlink, posix_whoami, getfacl and symlink. Using "-mNT1" reenabled them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still possible to connect to SMB1-only servers by default. sm...

...ensions are not required for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result some commands are not available, e.g. posix_encrypt, posix_open, posix_mkdir, posix_rmdir, posix_unlink, posix_whoami, getfacl and symlink. Using "-mNT1" reenabled them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still possible to connect to SMB1-only servers by default. sm...

...for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result, some commands are not available, e.g. 'posix_encrypt', 'posix_open', 'posix_mkdir', 'posix_rmdir', 'posix_unlink', 'posix_whoami', 'getfacl' and 'symlink'. Using "-mNT1" reenables them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still p...

...for encryption. The change to SMB3_11 as default also means smbclient no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result, some commands are not available, e.g. 'posix_encrypt', 'posix_open', 'posix_mkdir', 'posix_rmdir', 'posix_unlink', 'posix_whoami', 'getfacl' and 'symlink'. Using "-mNT1" reenables them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still p...

...tion. The change to SMB3_11 as default also means 'smbclient' no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result, some commands are not available, e.g. 'posix_encrypt', 'posix_open', 'posix_mkdir', 'posix_rmdir', 'posix_unlink', 'posix_whoami', 'getfacl' and 'symlink'. Using "-mNT1" reenables them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still p...

...tion. The change to SMB3_11 as default also means 'smbclient' no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result, some commands are not available, e.g. 'posix_encrypt', 'posix_open', 'posix_mkdir', 'posix_rmdir', 'posix_unlink', 'posix_whoami', 'getfacl' and 'symlink'. Using "-mNT1" reenables them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still p...

...tion. The change to SMB3_11 as default also means 'smbclient' no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result, some commands are not available, e.g. 'posix_encrypt', 'posix_open', 'posix_mkdir', 'posix_rmdir', 'posix_unlink', 'posix_whoami', 'getfacl' and 'symlink'. Using "-mNT1" reenables them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still p...

...tion. The change to SMB3_11 as default also means 'smbclient' no longer negotiates SMB1 unix extensions by default, when talking to a Samba server with "unix extensions = yes". As a result, some commands are not available, e.g. 'posix_encrypt', 'posix_open', 'posix_mkdir', 'posix_rmdir', 'posix_unlink', 'posix_whoami', 'getfacl' and 'symlink'. Using "-mNT1" reenables them, if the server supports SMB1. Note the default ("CORE") for "client min protocol" hasn't changed, so it's still p...