From 08c5b856a671b1583d3547dd76faf8a907485a12 Mon Sep 17 00:00:00 2001 From: Oyvind Albrigtsen Date: Thu, 19 Jun 2025 13:11:29 +0200 Subject: [PATCH] Filesystem: remove validate-all fstype check, as there isnt a reliable and portable way to check This check cause Warnings and might cause errors in future pcs versions when running "pcs resource create". Example: Warning: Validating resource options using the resource agent itself is enabled by default and produces warnings. In a future version, this might be changed to errors. Specify --agent-validation to switch to the future behavior. Warning: Validation result from agent: Jun 19 06:13:45 INFO: It seems we do not have ext3 support --- heartbeat/Filesystem | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/heartbeat/Filesystem b/heartbeat/Filesystem index d10e5a714..6d3960162 100755 --- a/heartbeat/Filesystem +++ b/heartbeat/Filesystem @@ -978,23 +978,6 @@ Filesystem_monitor() # Filesystem_validate_all() { - # Check if the $FSTYPE is workable - # NOTE: Without inserting the $FSTYPE module, this step may be imprecise - # TODO: This is Linux specific crap. - if [ ! -z "$FSTYPE" -a "$FSTYPE" != none ]; then - cut -f2 /proc/filesystems | grep "^${FSTYPE}$" >/dev/null 2>&1 - if [ $? -ne 0 ]; then - modpath=/lib/modules/$(uname -r) - moddep=$modpath/modules.dep - # Do we have $FSTYPE in modules.dep? - cut -d' ' -f1 $moddep \ - | grep "^${modpath}.*${FSTYPE}\.k\?o:$" >/dev/null 2>&1 - if [ $? -ne 0 ]; then - ocf_log info "It seems we do not have $FSTYPE support" - fi - fi - fi - # If we are supposed to do monitoring with status files, then # we need a utility to write in O_DIRECT mode. if [ $OCF_CHECK_LEVEL -gt 0 ]; then