Displaying 4 results from an estimated 4 matches for "a11f8bdbbceb".
2018 Apr 03
0
Sharding problem - multiple shard copies with mismatching gfids
...:07:57.979851] W [MSGID: 109009]
[dht-common.c:2831:dht_lookup_linkfile_cbk] 0-ovirt-350-zone1-dht:
/.shard/927c6620-848b-4064-8c88-68a332b645c2.3: gfid different on data
file on ovirt-350-zone1-replicate-3, gfid local =
00000000-0000-0000-0000-000000000000, 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-e7a...
2018 Apr 06
1
Sharding problem - multiple shard copies with mismatching gfids
...W [MSGID: 109009]
> [dht-common.c:2831:dht_lookup_linkfile_cbk] 0-ovirt-350-zone1-dht:
> /.shard/927c6620-848b-4064-8c88-68a332b645c2.3: gfid different on data
> file on ovirt-350-zone1-replicate-3, gfid local = 00000000-0000-0000-0000-000000000000,
> 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...
2018 Mar 26
1
Sharding problem - multiple shard copies with mismatching gfids
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
2018 Mar 26
3
Sharding problem - multiple shard copies with mismatching gfids
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,