Meeting date: 05/02/2018 (May 02nd, 2018), 19:30 IST, 14:00 UTC, 10:00 EDT
BJ Link
* Bridge: https://bluejeans.com/205933580
* Download:
Attendance
* Raghavendra M (Raghavendra Bhat), Kaleb, Atin, Amar, Nithya, Rafi, Shyam
Agenda
*
Commitment (GPLv2 Cure)
Hi,
One of the recent problems posted on gluster-devel regarding the ability to
view coredumps that occur during regression testing for patch acceptance was
discussed here [1].
Towards this, the core collection is now modified to collect system libraries
that were used by the executable that
From: Xavier Hernandez xhernan...@datalab.es
On Monday 30 June 2014 16:18:09 Shyamsundar Ranganathan wrote:
Will this rebalance on access feature be enabled always or only during
a
brick addition/removal to move files that do not go to the affected brick
while the main rebalance
Wanted to add to the thought process a different angle towards thinking about
the data classified volumes.
One of the reasons for classifying data (be it tiering or others, like high
profile users to high profile storage backends), is to deal with its (i.e data)
protection differently.
With
Hi Anders,
There are multiple problems that I see in the test provided, here is answering
one of them and the reason why this occurs. It does get into the code and
functions a bit, but bottom line is that on a code path the setattr that DHT
does, misses setting the SGID bit causing the problem
KP,
One way to view relevant information from the core would be as follow,
1) before loading the core you need to tell gdb to look for shared objects in a
different path,
- using 'set solib-search-path'
- For us this translates to 'set solib-search-path
You maybe looking at the problem being fixed here, [1].
On a lookup attribute mismatch was not being healed across directories, and
this patch attempts to address the same. Currently the version of the patch
does not heal the S_ISUID and S_ISGID bits, which is work in progress (but easy
enough
