similar to: Gluster + NFS-Ganesha Failover

Hi, after upgrading to 3.10.9 I'm seing ganesha.nfsd segfaulting all the time: [12407.918249] ganesha.nfsd[38104]: segfault at 0 ip 00007f872425fb00 sp 00007f867cefe5d0 error 4 in libglusterfs.so.0.0.1[7f8724223000+f1000] [12693.119259] ganesha.nfsd[3610]: segfault at 0 ip 00007f716d8f5b00 sp 00007f71367e15d0 error 4 in libglusterfs.so.0.0.1[7f716d8b9000+f1000] [14531.582667]

Hi Frank, It will be very easy to debug if u have core file with u. It looks like crash is coming from gfapi stack. If there is core file can u please share bt of the core file. Regards, Jiffin On Thursday 18 January 2018 11:18 PM, Frank Wall wrote: > Hi, > > after upgrading to 3.10.9 I'm seing ganesha.nfsd segfaulting all the time: > > [12407.918249] ganesha.nfsd[38104]:

The Gluster community is pleased to announce the release of Gluster 3.10.11 (packages available at [1]). Release notes for the release can be found at [2]. Thanks, Gluster community [1] Packages: https://download.gluster.org/pub/gluster/glusterfs/3.10/3.10.11/ [2] Release notes: http://docs.gluster.org/en/latest/release-notes/3.10.11/ _______________________________________________ Announce

Have sent a backport request https://review.gluster.org/19730 at release-3.10 branch. Hopefully this fix will be picked up in next update. On Fri, Mar 16, 2018 at 4:47 PM, Marco Lorenzo Crociani < marcoc at prismatelecomtesting.com> wrote: > Hi, > I'm hitting bug https://bugzilla.redhat.com/show_bug.cgi?id=1442983 > on glusterfs 3.10.11 and oVirt 4.1.9 (and before on glusterfs

Hi, I'm hitting bug https://bugzilla.redhat.com/show_bug.cgi?id=1442983 on glusterfs 3.10.11 and oVirt 4.1.9 (and before on glusterfs 3.8.14) The bug report says fixed in glusterfs-3.12.2-1 Is there a plan to backport the fix to 3.10.x releases or the only way to fix is upgrade to 3.12? Regards, -- Marco Crociani

Hi, this patch it's already available in the community version of gluster 3.12? In which version? If not, there is plan to backport it? Greetings, ??? Paolo Il 16/03/2018 13:24, Atin Mukherjee ha scritto: > Have sent a backport request https://review.gluster.org/19730 at > release-3.10 branch. Hopefully this fix will be picked up in next update. > > On Fri, Mar 16, 2018 at

On 16 October 2013 13:55, Daniel P. Berrange <berrange@redhat.com> wrote: > > Sounds like a host mis-configuration related to kernel bridge support > to me. > Could you tell me what might be mis-configured? I am using kernel 3.10.11, modules openvswitch, bridge, stp and llc are loaded. regards -- Maciej Gałkiewicz Shelly Cloud Sp. z o. o., Sysadmin http://shellycloud.com/,

I want to make you aware of a possible bug in the reflink handling of btrfs: When I reflink a file larger 2GB (on the same subvol), the reflinking fails. But it works fine for files smaller 2GB in size. I was able to track this down to btrfs with great support of Martin Raiber who created a small demo code: Source: https://urbackup.atlassian.net/secure/attachment/10201/reflink.cpp Compile: g++

On Wed, Oct 16, 2013 at 02:04:47PM +0200, Maciej Gałkiewicz wrote: > On 16 October 2013 13:55, Daniel P. Berrange <berrange@redhat.com> wrote: > > > > Sounds like a host mis-configuration related to kernel bridge support > > to me. > > > > Could you tell me what might be mis-configured? I am using kernel 3.10.11, > modules openvswitch, bridge, stp and llc

Package: blktap-dkms Version: 2.0.91-3 Severity: grave blktap-dkms depends on linux-headers-generic | linux-headers. linux-headers-generic never existed in Debian and linux-headers is a virtual package that is no longer provided, starting with Linux 3.11. This is because any level of dependency (Depends, Recommends or Suggests) on 'linux-headers' prevented APT auto-removing any of the

Hi all, I had been clearing the space cache on my btrfs vol (Debian 3.10.11-1 btrfs-tools 2013-7-5) by changing the fstab to "nospace_cache, clear_cache". I ran btrfsck --repair and it said: "cache and super generation don''t match, space cache will be invalidated." Can one of the dev''s please tell me whether that message means that the space cache

I have a system running the Debian package of 3.11.5 with an Amd Opteron 1212 processor (2*64bit cores), 8G of RAM, and an Intel 120G SSD for the root and home subvols. It has a RAID-1 array of 2*3TB disks for bulk storage (movies etc) but that probably isn''t relevant to this problem. On the root filesystem I have cron jobs making daily snapshots of / and /home and additional

Hi Kotresh, thanks for your repsonse... answers inside... best regards Dietmar Am 13.03.2018 um 06:38 schrieb Kotresh Hiremath Ravishankar: > Hi Dietmar, > > I am trying to understand the problem and have few questions. > > 1. Is trashcan enabled only on master volume? no, trashcan is also enabled on slave. settings are the same as on master but trashcan on slave is complete

Hi I am using Libvirt 1.1.2 with Openstack Havana (RC2, nova-network) and openvswitch 1.4.2+git20120612-9.1. Libvirt vif driver ( nova.virt.libvirt.vif.LibvirtGenericVIFDriver) generates config likes this: <interface type='bridge'> <mac address='fa:16:3e:44:30:a4'/> <source bridge='br0'/> <model type='virtio'/>

Hi Dietmar, I am trying to understand the problem and have few questions. 1. Is trashcan enabled only on master volume? 2. Does the 'rm -rf' done on master volume synced to slave ? 3. If trashcan is disabled, the issue goes away? The geo-rep error just says the it failed to create the directory "Oracle_VM_VirtualBox_Extension" on slave. Usually this would be because of gfid

Hello, in regard to https://bugzilla.redhat.com/show_bug.cgi?id=1434066 i have been faced to another issue when using the trashcan feature on a dist. repl. volume running a geo-replication. (gfs 3.12.6 on ubuntu 16.04.4) for e.g. removing an entire directory with subfolders : tron at gl-node1:/myvol-1/test1/b1$ rm -rf * afterwards listing files in the trashcan : tron at gl-node1:/myvol-1/test1$

https://bugs.freedesktop.org/show_bug.cgi?id=69488 Priority: medium Bug ID: 69488 Assignee: nouveau at lists.freedesktop.org Summary: GF108 (NVC1) GPU lockup QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: vekinn at gmail.com Hardware: Other