Updated glusterfs and redhat-storage-server packages that fix multiple bugs arenow available for use with the Red Hat Storage Server 2.1.

Red Hat Storage is software-only, scale-out storage that provides flexibleand affordable unstructured data storage for an enterprise. GlusterFS, akey building block of Red Hat Storage, is based on a stackable user-spacedesign and can deliver exceptional performance for diverse workloads.GlusterFS aggregates various storage servers over network interconnectionsinto one large, parallel network file system.This advisory addresses the following bugs:* Previously, the rebalance operation failed to migrate files if the volume had both quota and “features.quota-deem-statfs” option enabled. This was due to incorrect free space calculation. With this fix, the free space calculation issue is resolved and the rebalance operation migrates the files successfully.(#1168553)* Previously, executing the rebalance status command displayed incorrectvalues for the number of skipped and failed file migrations. With this fix, the command displays the correct values for the number of skipped and failed file migrations.(#1168552)* Previously, creating a new file over the SMB protocol, took a long time if the parent directory had many files in it. With this fix, the time takento create a new file over the SMB protocol takes lesser time, even if the parent directory has many files in it.(#1180130)* Previously, the Distributed Hash Table (DHT) Translator expected theindividual sub-volumes to return their local space consumption and availability during the file creation operation as part of min-free-disk calculation. When the quota-deem-statfs option was enabled on a volume, the quota translators on each of the bricks returned thevolume-wide space consumption and availability of disk space. This caused DHT to eventually always route all the file creationoperations to its first sub-volume, resulting in incorrect input valuesfor the min-free-disk calculation. With this fix, the load of the file creation operation is balanced correctly based on the min-free-disk criterion.(#1122920)* Previously, if the setuid bit of a file was set and if the file was migratedafter a remove-brick operation, the setuid bit did not exist after the file migration. With this fix, changes are made to ensure thatthe file permissions are retained with the setuid bit even afterfile migration.(#1168549)* Previously, the list of slave hosts were fetched only once during a Geo-replication start operation and the Geo-replication workers used that list to connect to the slave nodes. With this fix, after a slave nodefailure, a new list of slave nodes are retrieved and the Geo-replication worker chooses a different node to connect.(#1126798)* Previously, the buffer space considered for checking the total size ofthe slave clusters was not accurate. With this fix, the buffer size is increased and the calculation is accurate.(#1162140)* Previously, Geo-replication sessions failed to synchronize the ownershipsof empty files or files copied from other location. With this fix, files in both master and slave volumes have the same ownership and permission.(#1146256)* Previously, there was no API to verify if a Geo-replication session wasactive or not. A volume could not be stopped if a Geo-replicationsession exists, even if all the Geo-replication sessions were stopped corresponding to that volume. With this fix, APIs are provided toverify whether a Geo-replication session is active or stopped. (#1170048)* Previously, the status of a Geo-replication session would become defunctif the gsyncd.conf for a particular Geo-replication session had a missingstate-file or pid-file entry. With this fix, if entries like state-file orpid-file are missing in the gsyncd.conf or if the gsyncd.conf is also missing,gsyncd daemon looks for the missing configurations in thegsyncd_template.conf.(#1162142)Users of Red Hat Storage are advised to upgrade to these updated packages,which fix these issues.
Before applying this update, make sure all previously released erratarelevant to your system have been applied.This update is available via the Red Hat Network. Details on how touse the Red Hat Network to apply this update are available athttps://access.redhat.com/articles/11258Red Hat Storage Server 2.1

    MD5: 27f54d394416be52c3425a16eceb4336SHA-256: c0922663dacedd3bb285e80f865a582ab28ca6fa9c815d02c8eaf4eade78d7ed
    MD5: ee92f41bb45f58c4fd2c1a176aa752b8SHA-256: ae5eef8c43dd00501d72c82c89322869cc5d72ff11def60f8daa4140f357719b
    MD5: a3be8217a395e4a437b2773a6ff66124SHA-256: d41d7921955eec9683e0cad6912c6a749724db77cf0c9a06ff5c7ce048223e2f
    MD5: 70ee150658e71b508fea2946d5c4c237SHA-256: 631d3d71233845247748865131c2d3804b5032ed279ad0f7dcd520403def8f2a
    MD5: 234beb6a0337ec987ee5d49aa16e4729SHA-256: 73f8969ca1015a319df91567962bd650be02aa2540c2375d441fc1a9b73d46df
    MD5: 603029fbdac362a392f76b01e3e91a26SHA-256: c8dab53109074c5e80d482f8dd31967faac68c8efdb13d28b02ab62a2c894e72
    MD5: ce0cb146e88fd225ee6a9a5ef51e2198SHA-256: 3f34662b5ec965fd77d1e95edacf023fb38e8cf763629947cd22868405984048
    MD5: 0797a7e8e3ccbde8e6b98652622e753eSHA-256: 3ad7acdd5ccf6b60a319888495deb11763864c819ab09939f41d7c74b2299cf7
    MD5: dff09cecdee4d84795373ec9ab8c0ad4SHA-256: 51a0d1adad35259f6aea975b60f1faeb6dc29c6b30bde1f79e558c3a733a30af
    MD5: bc8d488945ff78674ec908effcf8afd1SHA-256: 017e577928aa1174e9c923b1a89fafd66afc67cfc6eb0ee53dd33dbe24f00d05
    MD5: f1338f4e632811a7ae529a21b0697177SHA-256: b85856e9f6ac7029bcd06736b31c919a425922d7c0c542587f0a3fafba2fd844
    MD5: f9d7a157d0a55cfd9731253a6b21f73cSHA-256: 281c74c210c8ffaa174aab285e7ac9c9bb861a929a3206ae4d8c53cff58a9adb
    MD5: d02bdf954030efa07028bd6fd387949aSHA-256: 4fa1c0051f9192dc213159b7bd9d50214582c0bbea0eeb2b6c4a35e76eb2a840
    MD5: 25b71313786f546fcca2a360fb8e2b09SHA-256: 284b91756d1fa06cd1f63fe9e63e9bd36b505169f6544e1a0fda3c2d6e1f79af
    MD5: dccac3b7e82ae7e9aa873a4e7291bb43SHA-256: aae6be0b9188b1e2f6ef81e10dc2d35b1d991344ffeddcab036fbea5d515e4f4
    MD5: 68e986c4d4604067d8a6e827be74e81cSHA-256: 0eca4b65edb3e1e30fa2b38b613be973a852af03b4eaec8bf2c5070ef86190f8
    MD5: 61150715108d2af0483cf3ad12c2d956SHA-256: a5b9ca4faf7b0aefbba9f0fa70769c7182fbb5aa9ce896a8994710525128206e
    MD5: 236af97d012f5997ff2c84d5662c1d55SHA-256: f04020100a09f50fecc0602423e1e45092208e148643bf5d49553f304163aa98
    MD5: cffc1efea3c31fca1b179550958c43a7SHA-256: b81404536626aad013b016f1a9f04358ec710247f75a26883fcccb56aaa7d0fe
    MD5: c4f246756b7673a22175a997f5de29bbSHA-256: c2886b13a4c8853a5f22669f03036e9049ef2aad785c3558dc956048cf2d74b6
    MD5: b90577a58f561bde5df6f08d30d8167dSHA-256: 84d5b3f1e055630056e57311a157eb37af92cd63eae20339783fa80bcad83051
    MD5: f9c948cdbbec61b4b017bec4ab69df43SHA-256: 21b5fcb2f283a2a0e9f0d2efe4ed21cce9bff86ab0482ffc7189d50d5fdb8573
    MD5: 28ceb3ea4759d12e372ee78374ea56f8SHA-256: b4c90fdfb7d0cf742c1455823e1a9268a04cd2f7084652b2d4f7175886897487
    MD5: 6e464d4c6223e0e782bb34368dca1adfSHA-256: 79c9080063e12aa42ec0ba9a266c6dfcbf8a9ed098a4325282ae7888855ceacd
    MD5: 73995465e97975af66ce6a60dc3d679cSHA-256: 549e7e43f989746281a59acf2c953da97befb917389e3b9b3e3baa71e97ddf70
    MD5: edb68be01d29f1e1a58458db045be62aSHA-256: 567ec4dc185a0421a9ea9d6d787547007ad0632457bedad5186df67fed599c53
    MD5: 16e08edeb008ed4bdc5fc5f33b4f8e3cSHA-256: 5ddfca7f6185bbd5eb1b92ba2c28f227b017ce2d75016e351e6b14ad053d39bf
    MD5: 03679703bb571330529545db6001abd8SHA-256: 6ed773953d406b0956eef2b81d33855ed129b8d20787f8f2dc3e62648801facb
(The unlinked packages above are only available from the Red Hat Network)
1146256 – Initial Georeplication fails to use correct GID on folders ONLY1168549 – Remove-brick: File permission (setuid) changes after migration of the file1168551 – DHT + rebalance :- log is full of warning ‘dict is NULL’1168552 – DHT + rebalance :- skipped file count is always ‘zero’ even though rebalance has skipped many files .1180130 – Files creates are very slow in directories already having files in it.

These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from:

Leave a Reply