[Bugs] [Bug 1207134] BitRot :- bitd is not signing Objects if more than 3 bricks are present on same node

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1207134

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|1186580                     |1227206 (glusterfs-3.7.2)
                   |(qe_tracker_everglades),    |
                   |1219955 (glusterfs-3.7.1),  |
                   |1221560, 1221605, 1224182,  |
                   |1224193, 1226146            |
             Blocks|                            |1221605
             Blocks|                            |1224193



--- Comment #12 from Niels de Vos <ndevos at redhat.com> ---
The required changes to fix this bug have not made it into glusterfs-3.7.1.
This bug is now getting tracked for glusterfs-3.7.2.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1219955
[Bug 1219955] GlusterFS 3.7.1 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1221560
[Bug 1221560] `-bash: fork: Cannot allocate memory' error seen regularly on
nodes on execution of any command
https://bugzilla.redhat.com/show_bug.cgi?id=1221605
[Bug 1221605] Scrub.log grows rapidly and the size increases upto 24GB in a
span of 10 hours
https://bugzilla.redhat.com/show_bug.cgi?id=1224182
[Bug 1224182] `-bash: fork: Cannot allocate memory' error seen regularly on
nodes on execution of any command
https://bugzilla.redhat.com/show_bug.cgi?id=1224193
[Bug 1224193] Scrub.log grows rapidly and the size increases upto 24GB in a
span of 10 hours
https://bugzilla.redhat.com/show_bug.cgi?id=1226146
[Bug 1226146] BitRot :- bitd is not signing Objects if more than 3 bricks
are present on same node
https://bugzilla.redhat.com/show_bug.cgi?id=1227206
[Bug 1227206] GlusterFS 3.7.2 tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the Docs Contact for the bug.