similar to: Help with disk server stability issues

Hi Mauro, We would require complete log file to debug this issue. Also, could you please provide some more information of the core after attaching to gdb and using command "bt". --- Ashish ----- Original Message ----- From: "Mauro Tridici" <mauro.tridici at cmcc.it> To: "Gluster Users" <gluster-users at gluster.org> Sent: Monday, September 25,

Dear Gluster Users, I implemented a distributed disperse 6x(4+2) gluster (v.3.10.5) volume with the following options: [root at s01 tier2]# gluster volume info Volume Name: tier2 Type: Distributed-Disperse Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c Status: Started Snapshot Count: 0 Number of Bricks: 6 x (4 + 2) = 36 Transport-type: tcp Bricks: Brick1: s01-stg:/gluster/mnt1/brick Brick2:

Hi, Following are the command to get the debug info for gluster - gdb /usr/local/sbin/glusterfs <core file path> Then on gdb prompt you need to type bt or backtrace (gdb) bt You can also provide the output of "thread apply all bt". (gdb) thread apply all bt Above commands should be executed on client node on which you have mounted the gluster volume and it crashed.

Hi Ashish, thank you for your answer. Do you need complete client log file only or something else in particular? Unfortunately, I never used ?bt? command. Could you please provide me an usage example string? I will provide all logs you need. Thank you again, Mauro > Il giorno 26 set 2017, alle ore 09:30, Ashish Pandey <aspandey at redhat.com> ha scritto: > > Hi Mauro, > >

Hi Ashish, I?m sorry to disturb you again, but I would like to know if you received the log files correctly. Thank you, Mauro Tridici > Il giorno 26 set 2017, alle ore 10:19, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto: > > > Hi Ashish, > > in attachment you can find the gdb output (with bt and thread outputs) and the complete log file until the crash happened.

Hi Ashish, in attachment you can find the gdb output (with bt and thread outputs) and the complete log file until the crash happened. Thank you for your support. Mauro Tridici > Il giorno 26 set 2017, alle ore 10:11, Ashish Pandey <aspandey at redhat.com> ha scritto: > > Hi, > > Following are the command to get the debug info for gluster - > gdb

Hi Nithya, thank you very much for your support and sorry for the late. Below you can find the output of ?gluster volume info tier2? command and the gluster software stack version: gluster volume info Volume Name: tier2 Type: Distributed-Disperse Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c Status: Started Snapshot Count: 0 Number of Bricks: 6 x (4 + 2) = 36 Transport-type: tcp Bricks:

Hi All, any news about this issue? Can I ignore this kind of error message or I have to do something to correct it? Thank you in advance and sorry for my insistence. Regards, Mauro > Il giorno 29 dic 2017, alle ore 11:45, Mauro Tridici <mauro.tridici at cmcc.it> ha scritto: > > > Hi Nithya, > > thank you very much for your support and sorry for the late. > Below

I think it is safe to ignore it. The problem exists? due to the minor difference in file time stamps in the backend bricks of the same sub volume (for a given file) and during the course of tar, the timestamp can be served from different bricks causing it to complain . The ctime xlator[1] feature once ready should fix this issue by storing time stamps as xattrs on the bricks. i.e. all bricks

Hi Ravi, thank you very much for your support and explanation. If I understand, the ctime xlator feature is not present in the current gluster package but it will be in the future release, right? Thank you again, Mauro > Il giorno 02 gen 2018, alle ore 12:53, Ravishankar N <ravishankar at redhat.com> ha scritto: > > I think it is safe to ignore it. The problem exists due to the

Hi Mauro, What version of Gluster are you running and what is your volume configuration? IIRC, this was seen because of mismatches in the ctime returned to the client. I don't think there were issues with the files but I will leave it to Ravi and Raghavendra to comment. Regards, Nithya On 29 December 2017 at 04:10, Mauro Tridici <mauro.tridici at cmcc.it> wrote: > > Hi All,

Dear All, in order to test my gluster volume performance, I started using gluster volume top command, but something is not clear to me. If I understand, gluster volume top command doesn?t measure in real time the ?weight? of my running workload, but it executed a ?dd? and mesaures the corresponding throughput. From the Admin Guide: "Viewing List of Write Performance on each Brick You can

Dear list, I hope this is not an old issue, but I couldn't find a solution even after google'ing quite some time. I try to migrate our institute's mail server (~200 users) from an old cyrus-based Mac installation to a new machine (NetBSD, dovecot 2.0.13). Everything went quite smoothly so far, but we are used to have "shared folders" ("public" folders in dovecot)

https://bugs.freedesktop.org/show_bug.cgi?id=102192 Bug ID: 102192 Summary: Dell XPS 15 9560: PU: 1 PID: 58 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/gf100.c:190 gf100_vm_flush+0x1b3/0x1c0 [nouveau] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All)

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Security Advisory 2005:808 https://rhn.redhat.com/errata/RHSA-2005-808.html This update is for the CENTOSPLUS repository only. We were waiting to roll in new code for the xfs file system from SGI, but that code is not yet ready. This release of the CENTOSPLUS kernel has the 2.6.9-22.0.1.EL code from upstream and is built like the previous CENTOSPLUS kernels with all the same

FYI, During my bi-weekly yum update, I noted the following warnings. Warnings during kernel update kernel-2.6.9-22.0.1.106.unsupported WARNING: /lib/modules/2.6.9-22.0.1.106.unsupported/kernel/fs/afs/kafs.ko needs unknown symbol afs_key_unregister WARNING: /lib/modules/2.6.9-22.0.1.106.unsupported/kernel/fs/afs/kafs.ko needs unknown symbol afs_key_register Is this anything to worry about? If I

CentOS Errata and Security Advisory 2005:808 https://rhn.redhat.com/errata/RHSA-2005-808.html This update is for the CENTOSPLUS repository only. We were waiting to roll in new code for the xfs file system from SGI, but that code is not yet ready. This release of the CENTOSPLUS kernel has the 2.6.9-22.0.1.EL code from upstream and is built like the previous CENTOSPLUS kernels with all the same

I''ve been attempting to update my dom0 kernel by using the 2.6.27 git tree from the xenclient repo and also to 2.6.30 using opensuse patches rebased by Andrew Lyon. In both cases there''s a problem with the 3ware 3w_9xxx driver incorrectly detecting the LUNs on the device or some other issue, which ultimately prevents partition table detection. In my testing I applied the

Hi all again, I found this kernel panic past days, now using the unsuported kernel and comes out again the same error. This time on '2.6.9-22.0.1.106.unsupported' kernel See attached logs, Env is the same with the same box, Hope it helps. TIA. JJ Garcia -------- Original Message -------- Subject: Kernel panic in usbserial. Date: Thu, 15 Dec 2005 12:09:53 +0100 From: J.J.Garcia