Skip to content

Mid: Filesystem: For block devices, allow monitor_10 even when specified by UID or LABEL. - #2216

Open
HideoYamauchi wants to merge 2 commits into
ClusterLabs:mainfrom
HideoYamauchi:change_monitor_10_take2
Open

HideoYamauchi wants to merge 2 commits into
ClusterLabs:mainfrom
HideoYamauchi:change_monitor_10_take2

Conversation

@HideoYamauchi

Copy link
Copy Markdown
Contributor

Hi Oyvind,
Hi All,

This modification is based on the discussion in the following issue.

It allows the monitor_10 processing to proceed when a match with blkid is found, even if UUID or LABEL is specified.

Best Reards,
Hideo Yamauchi.

Comment thread heartbeat/Filesystem Outdated
Comment thread heartbeat/Filesystem Outdated
return $OCF_ERR_CONFIGURED
fi
else
ocf_log warn "$DEVICE is not a block device, monitor 10 is noop"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also have to do the exit reason/CONFIGURED return here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oalbrigt

I’ve also modified the legacy processing.

If there are no issues, I’ll clean up the PR and resubmit it.
What do you think?

Many thanks,
Hideo Yamauchi

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oalbrigt
It looks like there is an error occurring in Jenkins.
The fix itself doesn't seem to be the problem, though...

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You dont have to resubmit it.

You can run git rebase -i HEAD~4 and change pick to s on the lines you want to merge into the first commit. Then you'll get mix and match any parts of the commit messages for the commit.

And finally you run git push -f and we should get the new commit instead of the 4 we have now.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. Jenkins is or was under maintenance today, so dont mind that failing when it's not related to the PR.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oalbrigt
I tried rebasing.

How does it look?

@HideoYamauchi
HideoYamauchi force-pushed the change_monitor_10_take2 branch from f0fd28b to 93ee94b Compare September 4, 2026 00:33
@HideoYamauchi

HideoYamauchi commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

@oalbrigt

It looks like there a points that need correction.
I will check it again.


I added a check because duplicate values ​​can be set for the device LABEL.
However, I believe this check should be performed at an earlier stage.
--> For example, checking right before the mount operation at startup.

What do you think?

Best Regards,
Hideo Yamauchi.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants