Thank you for making this happen. This is the first phase of adopting
a more GitHub based development workflow including actions.
On Thu, 12 Mar 2020 at 21:29, Deepshikha Khandelwal wrote:
>
> Hi everyone,
>
> We have migrated most of the current upstream bugs(attached below) from the
>
Hi everyone,
We have migrated most of the current upstream bugs(attached below) from the
GlusterFS community Bugzilla product to Github issues.
1. All the issues created as a part of a migration will have Bugzilla URL,
description, comments history, Github labels ('Migrated', 'Type: Bug',
Prio)
Hi,
One more question, I find each client has the same future time stamp where are
those time stamps from, since Since it is different from any brick stored time
stamp. And after I modify files from clients, it remains the same.
[root@mn-0:/home/robot]
# stat /mnt/export/testfile
File:
Hi,
This is abnormal test case, however, when this happened it will have big impact
on the apps using those files. And this can not be restored automatically
unless disable some xlator, I think it is unacceptable for the user apps.
cynthia
From: Kotresh Hiremath Ravishankar
Sent: 2020年3月12日
All the perf xlators depend on time (mostly mtime I guess). In my setup,
only quick read was enabled and hence disabling it worked for me.
All perf xlators needs to be disabled to make it work correctly. But I
still failed to understand how normal this kind of workload ?
Thanks,
Kotresh
On Thu,
