[Gluster-devel] Upstream nightly build on Centos is failing with glusterd crash

[Bala Konda Reddy Mekala]

Hi,
On fresh installation with the nightly build[1], "systemctl glusterd start"
is crashing with a glusterd crash (coredump). Bug was filed[2] and
centos-ci for glusto-tests is currently blocked because of the bug. Please
look into it.

Thanks,
Bala

[1] http://artifacts.ci.centos.org/gluster/nightly/master/7/x86_64/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1744420
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

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

Re: [Gluster-devel] [RFC] alter inode table lock from mutex to rwlock

[Changwei Ge]

Hi Amar,

Thanks for your reply, I will try it out then.


    -Changwei


On 2019/8/22 8:48 下午, Amar Tumballi Suryanarayan wrote:

Hi Changwei Ge,

On Thu, Aug 22, 2019 at 5:57 PM Changwei Ge > wrote:


Hi,

Now inode_table_t:lock is type of mutex which I think we can use
‘pthread_rwlock' to replace it for a better concurrency.

Because phread_rwlock allows more than one thread accessing inode
table
at the same time.
Moreover, the critical section the lock is protecting won't take many
CPU cycles and no I/O and CPU fault/exception involved after a quick
glance at glusterfs code.
I hope I didn't miss something.
If I would get an ACK from major glusterfs developer, I will try
to do it.


You are right. I believe this is possible. No harm in trying this out.

Xavier, Raghavendra, Pranith, Nithya, do you think this is possible?

Regards,

Thanks.
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

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



--
Amar Tumballi (amarts)

___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

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

[Gluster-devel] geo-replication won't start

[Nux!]

Hi,

I'm trying for the first time ever the geo-replication feature and I am 
not having much success (CentOS7, gluster 6.5).
First of all, from the docs I get the impression that I can 
geo-replicate over ssh to a simple dir, but it doesn't seem to be the 
case, the "slave" must be a gluster volume, doesn't it?


Second, the slave host is not in the subnet with the other gluster 
peers, but I reckon this would be the usual case and not a problem.


I've stopped the firewall on all peers and slave host to rule it out, 
but I can't get the georep started.


Creation is successfull, however STATUS won't change from Created.
I'm looking through all the logs and I can't see anything meaningful.

What steps could I take to debug this further?

Cheers,
Lucian


--
Sent from the Delta quadrant using Borg technology!
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

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

Re: [Gluster-devel] [RFC] alter inode table lock from mutex to rwlock

[Amar Tumballi Suryanarayan]

Hi Changwei Ge,

On Thu, Aug 22, 2019 at 5:57 PM Changwei Ge  wrote:

> Hi,
>
> Now inode_table_t:lock is type of mutex which I think we can use
> ‘pthread_rwlock' to replace it for a better concurrency.
>
> Because phread_rwlock allows more than one thread accessing inode table
> at the same time.
> Moreover, the critical section the lock is protecting won't take many
> CPU cycles and no I/O and CPU fault/exception involved after a quick
> glance at glusterfs code.
> I hope I didn't miss something.
> If I would get an ACK from major glusterfs developer, I will try to do it.
>
>
You are right. I believe this is possible. No harm in trying this out.

Xavier, Raghavendra, Pranith, Nithya, do you think this is possible?

Regards,



> Thanks.
> ___
>
> Community Meeting Calendar:
>
> APAC Schedule -
> Every 2nd and 4th Tuesday at 11:30 AM IST
> Bridge: https://bluejeans.com/836554017
>
> NA/EMEA Schedule -
> Every 1st and 3rd Tuesday at 01:00 PM EDT
> Bridge: https://bluejeans.com/486278655
>
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>
>

-- 
Amar Tumballi (amarts)
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

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

[Gluster-devel] [RFC] alter inode table lock from mutex to rwlock

[Changwei Ge]

Hi,

Now inode_table_t:lock is type of mutex which I think we can use 
‘pthread_rwlock' to replace it for a better concurrency.


Because phread_rwlock allows more than one thread accessing inode table 
at the same time.
Moreover, the critical section the lock is protecting won't take many 
CPU cycles and no I/O and CPU fault/exception involved after a quick 
glance at glusterfs code.

I hope I didn't miss something.
If I would get an ACK from major glusterfs developer, I will try to do it.

Thanks.
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

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

Re: [Gluster-devel] [Gluster-users] du output showing corrupt file system

[Jim Kinney]

Try running du not in the fuse mounted folder but in the folder on the server 
providing it.

On August 22, 2019 1:57:59 AM EDT, Amudhan P  wrote:
>Hi Jim,
>
>"du" command was run from fuse mounted volume. it's a single mount
>point.
>
>Gluster should handle that issue right and I don't have any problem in
>accessing issue reported folders but only when running "du" command for
>the
>folder it throws error msg.
>
>regards
>Amudhan
>
>
>On Wed, Aug 21, 2019 at 6:22 PM Jim Kinney 
>wrote:
>
>> Run the du command in the source space.
>>
>> A symlink that uses relative pathing can turn into a problem on a new
>> mount.
>>
>> That said, I've seen "too many levels of linking" errors associated
>with
>> the gfids dir .glusterfs and gfids of real dirs that are chained
>links to
>> other dirs. It's still a user space symlink error. It's just
>compounded by
>> gluster.
>>
>> On August 21, 2019 3:49:45 AM EDT, Amudhan P 
>wrote:
>>>
>>> it is definitely issue with gluster there is no symlink involved.
>>>
>>>
>>> On Tue, Aug 20, 2019 at 5:08 PM Jim Kinney 
>wrote:
>>>
 That's not necessarily a gluster issue. Users can create symlinks
>from a
 subdirectory up to a parent and that will create a loop.


 On August 20, 2019 2:22:44 AM EDT, Amudhan P 
 wrote:
>
> Hi,
>
> Can anyone suggest what could be the error and to fix this issue?
>
> regards
> Amudhan P
>
> On Sat, Aug 17, 2019 at 6:59 PM Amudhan P 
>wrote:
>
>> Hi,
>>
>> I am using Gluster version 3.10.1.
>>
>> Mounting volume through fuse mount and I have run the command du
>-hs
>> "directory" which holds many subdirectories.
>> some of the subdirectory given output with below message.
>>
>> du: WARNING: Circular directory structure.
>> This almost certainly means that you have a corrupted file
>system.
>> NOTIFY YOUR SYSTEM MANAGER.
>> The following directory is part of the cycle:
>>
>> what could be the issue or what should be done to fix this
>problem?
>>
>> regards
>> Amudhan P
>>
>>
 --
 Sent from my Android device with K-9 Mail. All tyopes are thumb
>related
 and reflect authenticity.

>>>
>> --
>> Sent from my Android device with K-9 Mail. All tyopes are thumb
>related
>> and reflect authenticity.
>>

-- 
Sent from my Android device with K-9 Mail. All tyopes are thumb related and 
reflect authenticity.___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

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