Currently trash xlator creates a inode table(1M) even if feature is not enabled. In brick_mux environment while 250 bricks are attached with a single brick process and feature is not enable brick process consumes 250M system memory unnecessarily per brick process.
The upstream committed patch link https://github.com/gluster/glusterfs/issues/1543
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1462