- Original Message -
> From: "Vijay Bellur"
> To: "Nithya Balachandran"
> Cc: "Gluster Devel"
> Sent: Wednesday, November 16, 2016 9:41:12 AM
> Subject: Re: [Gluster-devel] Upstream smoke test failures
>
> On Tue, Nov 15, 2016 at 8:40 AM, Nithya Balachandran
> wrote:
> >
> >
> > On 1
Hello folks,
I've pushed a few updates to fstat[1]:
Here are the visible updates:
* Add back the code for catching duplicate failure instance entry.
* Show review and patchset (linked to review).
* Show actual dates for the duration.
* Duration will now count from 00:00 of the date
* Show failure
Abhishek,
Here is the plan of action I suggest:
1. Set up a fresh cluster (say board A & board B) with 0 content in
/var/lib/glusterd and glusterd running with debug log mode (glusterd
-LDEBUG)
2. restart glusterd on board A (again with debug log mode)
3. check if you end up having multiple entri
Hi,
Sorry for late reply. I think I will wait for 3.10 LTS release to try
it. I am on 3.7.11 and it is very stable for us.
On Thu, Nov 17, 2016 at 1:05 PM, Pranith Kumar Karampuri
wrote:
>
>
> On Wed, Nov 16, 2016 at 11:47 PM, Serkan Çoban
> wrote:
>>
>> Hi,
>> Will disperse related new futures
On Mon, Nov 21, 2016 at 2:28 PM, Atin Mukherjee wrote:
>
>
> On Mon, Nov 21, 2016 at 10:00 AM, ABHISHEK PALIWAL <
> abhishpali...@gmail.com> wrote:
>
>> Hi Atin,
>>
>> System is the embedded system and these dates are before the system get
>> in timer sync.
>>
>> Yes, I have also seen these two f
On Mon, Nov 21, 2016 at 10:00 AM, ABHISHEK PALIWAL
wrote:
> Hi Atin,
>
> System is the embedded system and these dates are before the system get in
> timer sync.
>
> Yes, I have also seen these two files in peers directory on 002500 board
> and I want to know the reason why gluster creates the se
