Change-Id: I1f2d42f6c24ba55414888bcaf938a905e34ecb4d BUG: 1510012 Signed-off-by: ShyamsundarR <srangana@redhat.com>
Problem: Change GD_OP_VERSION to 3_13_0 from 3_12_0 for option storage.reserve
Solution: Actually feature was merged in 3.13.0 branch so GD_OP_VERSION needs
to change from 3_12_0 to 3_13_0
BUG: 1518512
Change-Id: I6f753978fd607919efcc60f73c37feaadc4f32ef
Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
Change-Id: I9801706f67332d6079e8ec58f9e08b332b35804a BUG: 1510012 Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
BUG: 1518744 Change-Id: Id7508eee3c0891d6e03cc2805facdc682a31f53d Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
NetBSD storage of extended attributes for UFS1 badly scales when the list of extended attributes names rises. gfid2path can add as many extended attributes names as we have files, hence we keep it disabled for performance sake. > Change-Id: Id77b5f5ceb4d5eba1b3362b4b9fc693450ffbc2b > Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org> > BUG: 1129939 Change-Id: I17c12251d80dbb41b7d4864d5739d1ad3d6877a0 Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org> BUG: 1513259
Problem: DISCARD operation on EC volume was punching hole of lesser size than the specified size in some cases. Solution: EC was not handling punch hole for tail part in some cases. Updated the code to handle it appropriately. >BUG: 1516206 >Change-Id: If3e69e417c3e5034afee04e78f5f78855e65f932 >Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com> BUG: 1518257 Change-Id: If3e69e417c3e5034afee04e78f5f78855e65f932 Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
Backport of: > BUG: 1515161 Change-Id: Ic1d2e17a7d14389b6734d1b88bd28c0a2907bbd6 BUG: 1517692 Signed-off-by: Xavier Hernandez <jahernan@redhat.com>
Problem: When eager-lock is on, and two writes happen in parallel on a FD we were observing the following behaviour: - First write fails on one data brick - Since the post-op is not yet happened, the inode refresh will get both the data bricks as readable and set it in the inode context - In flight split brain check see both the data bricks as readable and allows the second write - Second write fails on the other data brick - Now the post-op happens and marks both the data bricks as bad and arbiter will become source for healing Fix: Adding one more variable called write_suvol in inode context and it will have the in memory representation of the writable subvols. Inode refresh will not update this value and its lifetime is pre-op through unlock in the afr transaction. Initially the pre-op will set this value same as read_subvol in inode context and then in the in flight split brain check we will use this value instead of read_subvol. After all the checks we will update the value of this and set the read_subvol same as this to avoid having incorrect value in that. Change-Id: I2ef6904524ab91af861d59690974bbc529ab1af3 BUG: 1516313 Signed-off-by: karthik-us <ksubrahm@redhat.com> (cherry picked from commit 19f9bcff4aada589d4321356c2670ed283f02c03)
Problem: The heal info summary was printing the output at the end after crawling for pending heal entries completes on all the bricks. Fix: Printing the output immediately after the crawl on individual brick completes, so that it won't give the impression of CLI being hung. Change-Id: Ieaf5718736a7ee6837bac02bd30a95836e605dab BUG: 1514419 Signed-off-by: karthik-us <ksubrahm@redhat.com> (cherry picked from commit 77e3bc671aab2fda68ada53f38ec368b20675f59)
Change-Id: I1b6600cd519578faffe2f67ac0ee3e2555c3cb31 BUG: 1510012 Signed-off-by: ShyamsundarR <srangana@redhat.com> Signed-off-by: Niels de Vos <ndevos@redhat.com> Signed-off-by: karthik-us <ksubrahm@redhat.com> [ndevos: added "memory pool in statedump" and "glfs_mem_header" notes] [ksubrahm: added notes for "Addition of summary option to heal info"]