search for: 497e

...problem with one of my servers where the boot process fails, because it cannot find its root partition. My /boot/grub/grub.conf uses to look like ---8<--- title CentOS (2.6.32-431.17.1.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-431.17.1.el6.x86_64 ro root=UUID=8ef1f6cb-5dfc-497e-83d0-8d91cbbe4939 rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto rd_NO_DM rd_NO_LVM KEYBOARDTYPE=pc KEYTABLE=de initrd /initramfs-2.6.32-431.17.1.el6.x86_64.img ---8<-- I could get the system to boot again by just replacing the "root=UUI...

...gfid node = 55f86aa0-e7a0-4075-b46b-a11f8bdbbceb [2018-04-03 02:07:57.980716] W [MSGID: 109009] [dht-common.c:2570:dht_lookup_everywhere_cbk] 0-ovirt-350-zone1-dht: /.shard/927c6620-848b-4064-8c88-68a332b645c2.3: gfid differs on subvolume ovirt-350-zone1-replicate-3, gfid local = b1e3f299-32ff-497e-918b-090e957090f6, gfid node = 55f86aa0-e7a0-4075-b46b-a11f8bdbbceb [2018-04-03 02:07:57.980763] E [MSGID: 133010] [shard.c:1724:shard_common_lookup_shards_cbk] 0-ovirt-350-zone1-shard: Lookup on shard 3 failed. Base file gfid = 927c6620-848b-4064-8c88-68a332b645c2 [Stale file handle] [2018-04-...

...86aa0-e7a0-4075-b46b-a11f8bdbbceb > [2018-04-03 02:07:57.980716] W [MSGID: 109009] > [dht-common.c:2570:dht_lookup_everywhere_cbk] 0-ovirt-350-zone1-dht: > /.shard/927c6620-848b-4064-8c88-68a332b645c2.3: gfid differs on subvolume > ovirt-350-zone1-replicate-3, gfid local = b1e3f299-32ff-497e-918b-090e957090f6, > gfid node = 55f86aa0-e7a0-4075-b46b-a11f8bdbbceb > [2018-04-03 02:07:57.980763] E [MSGID: 133010] [shard.c:1724:shard_common_lookup_shards_cbk] > 0-ovirt-350-zone1-shard: Lookup on shard 3 failed. Base file gfid = > 927c6620-848b-4064-8c88-68a332b645c2 [Stale file h...

Ian, Do you've a reproducer for this bug? If not a specific one, a general outline of what operations where done on the file will help. regards, Raghavendra On Mon, Mar 26, 2018 at 12:55 PM, Raghavendra Gowdappa <rgowdapp at redhat.com> wrote: > > > On Mon, Mar 26, 2018 at 12:40 PM, Krutika Dhananjay <kdhananj at redhat.com> > wrote: > >> The gfid mismatch

On Mon, Mar 26, 2018 at 12:40 PM, Krutika Dhananjay <kdhananj at redhat.com> wrote: > The gfid mismatch here is between the shard and its "link-to" file, the > creation of which happens at a layer below that of shard translator on the > stack. > > Adding DHT devs to take a look. > Thanks Krutika. I assume shard doesn't do any dentry operations like rename,

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...59-48e3-96ca-60a988eb9358/9683B937E5AAC7C2882B5230E97EDBD7EF111B4C (171ead99-bee6-44cb-8078-3dc96e3d8562) on home-client-2 [2017-10-25 10:14:12.417280] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/6E672497EA8C4F5D6AD3FD95197C57A0982CAC35 (3ed02ef5-533a-4e8d-8e20-65cee501c2f9) on home-client-2 [2017-10-25 10:14:12.426709] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/18C31C98F76E19804C6ECA3DA89550B9D6451D9A...