I doubt there will be changes for OMV4. But for OMV5 you could put an issue or PR here:
dig into the code and it looks like here it is taking only /dev/sd.. device :
I think, you are right.
I was wondering why autoshutdown was not working when I had disk activity on my RAID 6.
The same situation here with a ZFS pool. A running ZFS scrub is also not detected by the autoshutdown plugin. It must be detected by another method.
Therefore in your case the system activity on your raid must be detected by an alternative way (e.g. in expert mode "plugincheck"). Look at the example in the autoshutdown readme: Autoshutdown readme
In my opinion, if you are using any kind of raid, you need availability and would not be shutting your system down. Having to re-assemble your pool on every boot is just asking for trouble.
In my opinion, it would still be desirable if Autoshutdown plugin could deal with raid- and ZFS-constellations (btrfs ?). Even if pure teaching says that this type of systems should run 24/7. No offence!
t would still be desirable if Autoshutdown plugin could deal with raid- and ZFS-constellations (btrfs ?). Even if pure teaching says that this type of systems should run 24/7. No offence!
That's fine but someone else will have to make the change. I don't even want to maintain this plugin anymore because I can't test it and it needs a lot of work that I don't want to spend time on.
I don't even want to maintain this plugin anymore
That would be a real pity, because in my opinion it is a very useful plugin.
That would be a real pity, because in my opinion it is a very useful plugin.
How can I maintain it?
Sorry, but I don´t understand your question.
I said it would be regrettable if the plugin is not maintained at all anymore and would therefore no longer be available in future OMV versions.
Sorry, but I don´t understand your question.
I said it would be regrettable if the plugin is not maintained at all anymore and would therefore no longer be available in future OMV versions.
You said it was a pity that it wouldn't be maintained. I took that as I was making a bad decision. Therefore, I asked how would I be able to maintain if I don't use it and can't test it. That doesn't seem to be what you meant. And I should be able to make the plugin itself work with the next version of OMV if someone will maintain the script. But I need people to test the thing. There have been pull requests to fix things but I spend more time begging people to test the damn thing than I want. If this script is so important, people have to step up and test.
Ok, I understand now. Then we have to assume that the autoshutdown plugin is no longer included in later OMV versions. The problem you describe will then obviously affect all plugins that you are not using yourself.
hen we have to assume that the autoshutdown plugin is no longer included in later OMV versions.
No, I said I would port the plugin to future OMV versions. I just can't make sure the autoshutdown.sh script will be working correctly.
The problem you describe will then obviously affect all plugins that you are not using yourself.
If that were true, there would be almost no omv-extras plugins. I don't use most of them but I can test them. Therefore I am maintaining them.
Don’t have an account yet? Register yourself now and be a part of our community!
