snapshot-resync-target-lvm.sh: disable devicesfile when calling lvm#59
Open
Nowa-Ammerlaan wants to merge 1 commit intoLINBIT:masterfrom
Open
snapshot-resync-target-lvm.sh: disable devicesfile when calling lvm#59Nowa-Ammerlaan wants to merge 1 commit intoLINBIT:masterfrom
Nowa-Ammerlaan wants to merge 1 commit intoLINBIT:masterfrom
Conversation
In Red Hat 9+, the devices/use_devicesfile setting is enabled by default (=1). However when the devicesfile is enabled, the devices/filter and devices/global_filter are ineffective. Running this command manually results in the following warning: > Please remove the lvm.conf filter, it is ignored with the devices This has the unfortunate side-effect of triggering the hanging lvm commands that this filter is intending to avoid. We have seen on our machines that after a reboot drbd fails to connect. It claims there is a network error while in reality the lvm commands run in this script are hanging until a timeout occurs. Disabling the devices/use_devicesfile setting (=0) in lvm.conf resolved this problem. The DRBD-9 documentation makes no mention of the devices/use_devicesfile setting. It mentions the filter and global_filter, but with the Red Hat 9+ default setting of devices/use_devicesfile=1 neither of these settings is actually effective. The documentation does mention the devices/write_cache_state setting, but this setting was removed in lvm v2.03. I therefore feel the documentation might need to be updated. This change works around the original problem we encountered by ensuring that the devices/use_devicesfile setting is disabled when running the lvm commands in the snapshot-resync-target-lvm.sh script. This works as an alternative to globally disabling the devicesfile in /etc/lvm/lvm.conf. Signed-off-by: Nowa Ammerlaan <nowa.ammerlaan@surf.nl>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In Red Hat 9+, the
devices/use_devicesfilesetting is enabled by default (=1). However when the devicesfile is enabled, thedevices/filteranddevices/global_filterare ineffective.Running this command manually results in the following warning:
This has the unfortunate side-effect of triggering the hanging lvm commands that this filter is intending to avoid. We have seen on our machines that after a reboot drbd fails to connect. It claims there is a network error while in reality the lvm commands run in this script are hanging until a timeout occurs. Disabling the
devices/use_devicesfilesetting (=0) inlvm.confresolved this problem.The DRBD-9 documentation makes no mention of the
devices/use_devicesfilesetting. It mentions the filter and global_filter, but with the Red Hat 9+ default setting ofdevices/use_devicesfile=1neither of these settings is actually effective. The documentation does mention thedevices/write_cache_statesetting, but this setting was removed in lvm v2.03. I therefore feel the documentation might need to be updated.This change works around the original problem we encountered by ensuring that the
devices/use_devicesfilesetting is disabled when running the lvm commands in thesnapshot-resync-target-lvm.shscript. This works as an alternative to globally disabling the devicesfile in/etc/lvm/lvm.conf.