Raised https://bugzilla.redhat.com/show_bug.cgi?id=1405301 and
https://bugzilla.redhat.com/show_bug.cgi?id=1405305 for master and
release-3.9 respectively.
I've sent patches to move this test under the bad tests category until
Niels' patch fixes the crash.
This is to prevent the two patches on
Proposal to add one more byte to GFID to store "Type" information.
Extra byte will represent type(directory: 00, file: 01, Symlink: 02
etc)
For example, if a directory GFID is f4f18c02-0360-4cdc-8c00-0164e49a7afd
then, GFID2 will be 00f4f18c02-0360-4cdc-8c00-0164e49a7afd.
Changes to Backend
On 12/15/2016 01:41 PM, Nithya Balachandran wrote:
On 15 December 2016 at 18:07, Xavier Hernandez > wrote:
On 12/15/2016 12:48 PM, Raghavendra Gowdappa wrote:
I need to step back a little to understand the RCA correctly.
On 15 December 2016 at 18:07, Xavier Hernandez
wrote:
> On 12/15/2016 12:48 PM, Raghavendra Gowdappa wrote:
>
>> I need to step back a little to understand the RCA correctly.
>>
>> If I understand the code correctly, the callstack which resulted in
>> failed setattr is (in
On 12/15/2016 12:48 PM, Raghavendra Gowdappa wrote:
I need to step back a little to understand the RCA correctly.
If I understand the code correctly, the callstack which resulted in failed
setattr is (in rebalance process):
dht_lookup -> dht_lookup_cbk -> dht_lookup_everwhere ->
On Thu, Dec 15, 2016 at 05:20:26PM +0530, Nigel Babu wrote:
> Hello folks,
>
> This is a request for feedback for this plan to build a pipeline that will go
> from a commit to builds that are tested and signed. While the
> nightly.gluster.org site will be up by the time 3.10 is released, we will
Good that you asked. I'll try but be warned this will involve me coming back
to you with lot more questions. :)
I've been trying this for the past two days (not to mention the fio run
takes
really long) and so far there has been no crash/assert failure.
If you already have the core:
in frame 1,
Hello folks,
This is a request for feedback for this plan to build a pipeline that will go
from a commit to builds that are tested and signed. While the
nightly.gluster.org site will be up by the time 3.10 is released, we will not
yet be automating releases with this pipeline by then.
# Why
*
I need to step back a little to understand the RCA correctly.
If I understand the code correctly, the callstack which resulted in failed
setattr is (in rebalance process):
dht_lookup -> dht_lookup_cbk -> dht_lookup_everwhere ->
dht_lookup_everywhere_cbk -> dht_lookup_everywhere_done ->
On Wed, 2016-11-23 at 17:44 -0500, Jeff Darcy wrote:
> > The end of the long dark tunnel might be in sight. I've been working on
> > snapshots, and have only two tests that fail. One's for XML output, so
> > I'm not even sure I care.
>
> With the version of the patch I pushed a few minutes ago,
Hi,
Yesterday I created a small utility to scan the brick and find issues
with directories created by Gluster. Tool can detect following issues
- No GFID: If a directory in brick backend doesn't have `trusted.gfid` xattr
- No Parent GFID: Parent directory doesn't have a `trusted.gfid` xattr
-
11 matches
Mail list logo