Tamar Shacked

Results 14 comments of Tamar Shacked

Hi @olegkrutov , - I dont see errors from rebalance output and as no bricks were added or removed rebalance had no layout to fix or file(s) to migrate. >...

> So isn't there any feature to migrate some files from full brick to one having more space? Maybe manually setting some xattrs or so? There's no feature that migrate...

> Hi @tshacked, thank you for your reply. But did you mean "move" instead of "copy"? Yes, I meant move > And do I need to set some xattrs of...

> /var/log/glusterfs/bricks/bricks-8e953fb6-c0d2-40e0-831d-f67965186915-brick.log.1:[2022-03-14 16:24:47.687322 +0000] E [MSGID: 113001] [posix-helpers.c:1273:posix_handle_pair] 0-dc4-posix: /bricks/8e953fb6-c0d2-40e0-831d-f67965186915/brick/.glusterfs/4a/d4/4ad4d646-6f36-4849-bd17-0d12fd67152d: key:glusterfs.inodelk-dom-countflags: 0 length:16 [Operation not supported] > /var/log/glusterfs/bricks/bricks-8e953fb6-c0d2-40e0-831d-f67965186915-brick.log.1:[2022-03-14 16:24:48.567089 +0000] E [MSGID: 113001] [posix-helpers.c:1273:posix_handle_pair] 0-dc4-posix: /bricks/8e953fb6-c0d2-40e0-831d-f67965186915/brick/.glusterfs/4a/d4/4ad4d646-6f36-4849-bd17-0d12fd67152d: key:glusterfs.inodelk-dom-countflags: 0 length:16 [Operation...

> This particular files has 2 copies + 2 linkto > > ``` > ls /mnt/volume/data/queues > ... > -rw-rw-r-- 1 user users 3087081 Nov 7 2019 label-full-defect-qa-20191107.json > -rw-rw-r--...

> Or do you have any more insight in to the cause or is there any more information we can provide? Many files were not rebalanced to the correct subvol...

Hi @smremde > > Any update on the issue or a work around? If this is a race condition, could we start the rebalance and kill the rebalance process on...

> @tshacked > > > 1 - rebalance/brick logs from all nodes > > 2 - list the xattr of a problematic file > > The problem is, this will...

General comment: The typedef for the shared_ptr declare in LogSegment.h: `using LogSegmentRef = std::shared_ptr;` I didn"t find a way to enable forward declaration for it. So I'd to explicitly use...

> > You might have to exhaustively check for those cases and explicitly include the `LogSegment.h` header to make the `LogSegmentRef` definition available appropriately. > > OR > > You'll...