Description of problem: ----------------------- According to Dennis Keefe, Use these xfs settings for XFS in RHHI, so that XFS handle conditions when VDO runs out of physical space. echo 4 | tee /sys/fs/xfs/dm-13/error/metadata/ENOSPC/max_retries echo 4 | tee /sys/fs/xfs/dm-13/error/metadata/EIO/max_retries Gdeploy bug ( BZ 1523562 ) was fixed to solve this request, but it turned out to be that these values are not persisted in the config files - max_retries This bug is required to make these changes persistent.
Sahina, As explained towards the end of comment0, the original issue is solved, where the max_retries under ENOSPC and EIO were updated to 4. But these values are not persisted. So opened this bug, but by mistake, did the cloning and missed to change the subject and context
We need a change in RHEL to persist this setting. Sas, have you opened a corresponding bug for this?
(In reply to Sahina Bose from comment #2) > We need a change in RHEL to persist this setting. Sas, have you opened a > corresponding bug for this? Sahina, Yes, there is already a RHEL XFS bug opened, but connected as 'depends on' on this bug. I have made the required changes now to reflect that on this bug Here is the bug - https://bugzilla.redhat.com/show_bug.cgi?id=1578354
I did some testing in RHEL 7.5, and found that the default settings of XFS no longer retry forever, which means that the "error/metadata/ENOSPC" and "error/metadata/EIO" settings no longer need to be made on each mount. After an "out of physical space" condition, all that needs to be done is umount, add space to the backing device of VDO (i.e.: resize partition, lvextend, etc.), run "vdo --growPhysical", then mount the filesystem on the VDO volume, and run xfs_growfs. Therefore, there's no need to persist the setting in RHEL 7.5.
Closing as this is no longer required