So it is working again? If you download the package again, I am curious if it works without /var/spool now. If you don't want to break things again, i understand.
So what should I do now? Install the test version again?
So it is working again? If you download the package again, I am curious if it works without /var/spool now. If you don't want to break things again, i understand.
So what should I do now? Install the test version again?
So it is working again? If you download the package again, I am curious if it works without /var/spool now. If you don't want to break things again, i understand.
Yes. After I removed the test version of Flash 7.1, the mail worked. I rebooted the server and everything was OK. Then I reinstalled the test Flash 7.1 and the mail still works. Maybe my mistake was that the first time I installed Flash 7.1 on top of Flash 7.0.1... I will continue to observe, but so far everything works...
Then I reinstalled the test Flash 7.1 and the mail still works. Maybe my mistake was that the first time I installed Flash 7.1 on top of Flash 7.0.1... I will continue to observe, but so far everything works
I can see how the upgrade might cause an issue. Glad to hear it works.
I just tried the latest version of the plugin. Still breaks things here. I have some rsyslog events that generate emails but those stop working with the plugin installed. When I uninstall the plugin I get mailbombed with all those pending notices.
I just tried the latest version of the plugin. Still breaks things here. I have some rsyslog events that generate emails but those stop working with the plugin installed. When I uninstall the plugin I get mailbombed with all those pending notices.
Are you installing the plugin from the repository, or the latest test version of 7.1? I currently have 7.1 working as it should...
It's been working for almost two hours and everything is still ok...
root@omv420:~# journalctl -u postfix@-.service
Jan 10 17:45:32 omv420 systemd[1]: Stopping postfix@-.service - Postfix Mail Transport Agent (instance -)...
Jan 10 17:45:32 omv420 postfix/master[1452]: terminating on signal 15
Jan 10 17:45:32 omv420 systemd[1]: postfix@-.service: Deactivated successfully.
Jan 10 17:45:32 omv420 systemd[1]: Stopped postfix@-.service - Postfix Mail Transport Agent (instance -).
Jan 10 17:45:32 omv420 systemd[1]: postfix@-.service: Consumed 1.874s CPU time.
-- Boot 82718fa2014f4ac684470db28d9554f1 --
Jan 10 17:49:25 omv420 systemd[1]: Starting postfix@-.service - Postfix Mail Transport Agent (instance -)...
Jan 10 17:49:30 omv420 postfix/master[1408]: daemon started -- version 3.7.11, configuration /etc/postfix
Jan 10 17:49:30 omv420 systemd[1]: Started postfix@-.service - Postfix Mail Transport Agent (instance -).
Jan 10 17:50:01 omv420 postfix/pickup[1409]: 27E20E088D: uid=0 from=<root>
Jan 10 17:50:01 omv420 postfix/cleanup[3416]: 27E20E088D: message-id=<20250110155001.27E20E088D@omv420..org>
Jan 10 17:50:01 omv420 postfix/qmgr[1410]: 27E20E088D: from=<omv420@.org>, size=404, nrcpt=2 (queue active)
Jan 10 17:50:01 omv420 postfix/pipe[3428]: 27E20E088D: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.24, delays=0.18/0.02/0/0.04, dsn=2.0.0, status=sent (delivered via omvnotificationfilter>
Jan 10 17:50:01 omv420 postfix/smtp[3429]: 27E20E088D: replace: header Subject: Test message from omv420: Subject: [omv420..org] Test message from omv420
Jan 10 17:50:01 omv420 postfix/smtp[3429]: 27E20E088D: to=<zzz@zzz.org>, relay=mail.zzz.org[91.194.250.246]:465, delay=0.4, delays=0.18/0.14/0.08/0.01, dsn=2.0.0, status=sent (250 2.0.0 678141a9-0000092a Message accepted for >
Jan 10 17:50:01 omv420 postfix/qmgr[1410]: 27E20E088D: removed
Jan 10 17:50:35 omv420 postfix/smtpd[3577]: connect from localhost.localdomain[127.0.0.1]
Jan 10 17:50:35 omv420 postfix/smtpd[3577]: 75E0BE0853: client=localhost.localdomain[127.0.0.1]
Jan 10 17:50:35 omv420 postfix/cleanup[3416]: 75E0BE0853: message-id=<1736524235.655380bb1f2299ad@omv420>
Jan 10 17:50:35 omv420 postfix/qmgr[1410]: 75E0BE0853: from=<omv420@zzz.org>, size=1032, nrcpt=2 (queue active)
Jan 10 17:50:35 omv420 postfix/smtpd[3577]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jan 10 17:50:35 omv420 postfix/pipe[3428]: 75E0BE0853: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.1, delays=0.06/0/0/0.04, dsn=2.0.0, status=sent (delivered via omvnotificationfilter ser>
Jan 10 17:50:35 omv420 postfix/smtp[3429]: 75E0BE0853: replace: header Subject: Monitoring alert -- Status failed mountpointsrv-rem: Subject: [omv420.zzz.org] Monitoring alert -- Status failed mountpointsrv-remotemount-ROON
Jan 10 17:50:35 omv420 postfix/smtp[3429]: 75E0BE0853: to=<zzz@zzz.org>, relay=mail.zzz.org[91.194.250.246]:465, delay=0.16, delays=0.06/0/0.08/0.01, dsn=2.0.0, status=sent (250 2.0.0 678141cb-0000092b Message accepted for de>
Jan 10 17:50:35 omv420 postfix/qmgr[1410]: 75E0BE0853: removed
Jan 10 17:51:05 omv420 postfix/smtpd[3577]: connect from localhost.localdomain[127.0.0.1]
Jan 10 17:51:05 omv420 postfix/smtpd[3577]: B5A0FE0853: client=localhost.localdomain[127.0.0.1]
Jan 10 17:51:05 omv420 postfix/cleanup[3416]: B5A0FE0853: message-id=<1736524265.2134b9fb683c887e@omv420>
Jan 10 17:51:05 omv420 postfix/smtpd[3577]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jan 10 17:51:05 omv420 postfix/qmgr[1410]: B5A0FE0853: from=<omv420@zzz.org>, size=1030, nrcpt=2 (queue active)
Jan 10 17:51:05 omv420 postfix/pipe[3428]: B5A0FE0853: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.1, delays=0.06/0/0/0.04, dsn=2.0.0, status=sent (delivered via omvnotificationfilter ser>
Jan 10 17:51:05 omv420 postfix/smtp[3429]: B5A0FE0853: replace: header Subject: Monitoring exec -- Status failed mountpointsrv-remo: Subject: [omv420.zzz.org] Monitoring exec -- Status failed mountpointsrv-remotemount-ROON
Jan 10 17:51:05 omv420 postfix/smtp[3429]: B5A0FE0853: to=<zzz@zzz.org>, relay=mail.zzz.org[91.194.250.246]:465, delay=0.16, delays=0.06/0/0.08/0.01, dsn=2.0.0, status=sent (250 2.0.0 678141e9-0000092c Message accepted for de>
Jan 10 17:51:05 omv420 postfix/qmgr[1410]: B5A0FE0853: removed
Jan 10 17:53:07 omv420 postfix/pickup[1409]: 05CDBE0A57: uid=0 from=<root>
Jan 10 17:53:07 omv420 postfix/cleanup[5379]: 05CDBE0A57: message-id=<20250110155307.05CDBE0A57@omv420.zzz.org>
Jan 10 17:53:07 omv420 postfix/qmgr[1410]: 05CDBE0A57: from=<omv420@zzz.org>, size=404, nrcpt=2 (queue active)
Jan 10 17:53:07 omv420 postfix/pipe[5381]: 05CDBE0A57: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.11, delays=0.06/0.01/0/0.04, dsn=2.0.0, status=sent (delivered via omvnotificationfilter>
Jan 10 17:53:07 omv420 postfix/smtp[5382]: 05CDBE0A57: replace: header Subject: Test message from omv420: Subject: [omv420.zzz.org] Test message from omv420
Jan 10 17:53:07 omv420 postfix/smtp[5382]: 05CDBE0A57: to=<zzz@zzz.org>, relay=mail.zzz.org[91.194.250.246]:465, delay=0.24, delays=0.06/0.1/0.08/0.01, dsn=2.0.0, status=sent (250 2.0.0 67814263-0000092d Message accepted for >
Jan 10 17:53:07 omv420 postfix/qmgr[1410]: 05CDBE0A57: removed
Jan 10 18:38:17 omv420 postfix/pickup[1409]: 5C398E0A58: uid=0 from=<root>
Jan 10 18:38:17 omv420 postfix/cleanup[10850]: 5C398E0A58: message-id=<20250110163817.5C398E0A58@omv420.zzz.org>
Jan 10 18:38:17 omv420 postfix/qmgr[1410]: 5C398E0A58: from=<omv420@zzz.org>, size=404, nrcpt=2 (queue active)
Jan 10 18:38:17 omv420 postfix/pipe[10852]: 5C398E0A58: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.1, delays=0.05/0.01/0/0.04, dsn=2.0.0, status=sent (delivered via omvnotificationfilter>
Jan 10 18:38:17 omv420 postfix/smtp[10853]: 5C398E0A58: replace: header Subject: Test message from omv420: Subject: [omv420.zzz.org] Test message from omv420
Jan 10 18:38:17 omv420 postfix/smtp[10853]: 5C398E0A58: to=<zzz@zzz.org>, relay=mail.zzz.org[91.194.250.246]:465, delay=0.24, delays=0.05/0.1/0.08/0.01, dsn=2.0.0, status=sent (250 2.0.0 67814cf9-00000939 Message accepted for>
Jan 10 18:38:17 omv420 postfix/qmgr[1410]: 5C398E0A58: removed
Jan 10 19:36:04 omv420 postfix/pickup[18057]: D2C6CE0A58: uid=0 from=<root>
Jan 10 19:36:04 omv420 postfix/cleanup[20021]: D2C6CE0A58: message-id=<20250110173604.D2C6CE0A58@omv420.zzz.org>
Jan 10 19:36:04 omv420 postfix/qmgr[1410]: D2C6CE0A58: from=<omv420@zzz.org>, size=404, nrcpt=2 (queue active)
Jan 10 19:36:04 omv420 postfix/pipe[20023]: D2C6CE0A58: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.1, delays=0.06/0.01/0/0.04, dsn=2.0.0, status=sent (delivered via omvnotificationfilter>
Jan 10 19:36:05 omv420 postfix/smtp[20024]: D2C6CE0A58: replace: header Subject: Test message from omv420: Subject: [omv420.zzz.org] Test message from omv420
Display More
Are you installing the plugin from the repository, or the latest test version of 7.1? I currently have 7.1 working as it should...
It's been working for almost two hours and everything is still ok...
I am installing the latest test version 7.1.
I am installing the latest test version 7.1.
My system is now as in the screenshots. Mail works...
Mail works...
I have five systems with it installed and the mail works. I can't figure out why it doesn't work on some systems.
I have five systems with it installed and the mail works. I can't figure out why it doesn't work on some systems.
Well, if it's any consolation I have been stumped since it broke last year sometime. ![]()
I applied the latest version to one of my RPI's, and it seems to be working so far. After rebooting, I triggered a couple of test notifications, and they came through immediately. I applied the new version on top of the old one (v7.0.1), and it appeared to properly uninstall the previous version before installing. Having said that, the old version still appears to be installed in Plugins. I'll keep testing, and if notifications stop working, I'll perform a proper uninstall of the old version and reinstall of the new version.
Interestingly, my other RPi seems to be working OK without the new version. The only real difference between the two is that one has 4GB RAM while the other has 8GB. Otherwise, they are both RPi 4's running completely up-to-date OMV instances.
Thanks ryecoaaron for the instructions and continued assistance.
Having said that, the old version still appears to be installed in Plugins
What is the output of: dpkg -l | grep -E "openme|folder2ram"
What is the output of: dpkg -l | grep -E "openme|folder2ram"
You didn't want to post all the output? I'm surprised folder2ram is still installed. The 7.1 flashmemory plugin kicks off a background job to uninstall it. Installing the flashmemory plugin again should remove it. I did just upload a significant change in the 7.1 plugin. It adds a datatable for each zram directory. This will allow people to edit the size of the mounts, add or remove mounts, and remove swap if they don't need it.
ryecoaaron Hello! Today I had a new problem with the test version 7.1. Today there was a big update that included a kernel update. I installed it via the command - omv-upgrade. At the end of the update I got an error:
Setting up linux-image-6.1.0-29-amd64 (6.1.123-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-28-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-28-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-29-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-29-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-29-amd64
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-6.1.0-29-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-29-amd64 (--configure):
installed linux-image-6.1.0-29-amd64 package post-installation script subprocess returned error exit status 1
Setting up systemd-resolved (252.33-1~deb12u1) ...
Setting up python3.11-minimal (3.11.2-6+deb12u5) ...
Setting up openssh-sftp-server (1:9.2p1-2+deb12u4) ...
Setting up openssh-server (1:9.2p1-2+deb12u4) ...
Creating config file /tmp/_etc_ssh_sshd_config with new version
rescue-ssh.target is a disabled or a static unit not running, not starting it.
ssh.socket is a disabled or a static unit not running, not starting it.
Setting up libpython3.11-stdlib:amd64 (3.11.2-6+deb12u5) ...
Setting up libavahi-common3:amd64 (0.8-10+deb12u1) ...
dpkg: dependency problems prevent configuration of linux-image-amd64:
linux-image-amd64 depends on linux-image-6.1.0-29-amd64 (= 6.1.123-1); however:
Package linux-image-6.1.0-29-amd64 is not configured yet.
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Setting up nfs-common (1:2.6.2-4+deb12u1) ...
Creating config file /tmp/_etc_idmapd.conf with new version
auth-rpcgss-module.service is a disabled or a static unit not running, not starting it.
nfs-utils.service is a disabled or a static unit not running, not starting it.
rpc-gssd.service is a disabled or a static unit not running, not starting it.
rpc-svcgssd.service is a disabled or a static unit not running, not starting it.
var-lib-nfs-rpc_pipefs.mount is a disabled or a static unit not running, not starting it.
Setting up libavahi-core7:amd64 (0.8-10+deb12u1) ...
Setting up libnss-resolve:amd64 (252.33-1~deb12u1) ...
Setting up libavahi-client3:amd64 (0.8-10+deb12u1) ...
Setting up python3.11 (3.11.2-6+deb12u5) ...
Setting up nfs-kernel-server (1:2.6.2-4+deb12u1) ...
nfs-blkmap.service is a disabled or a static unit not running, not starting it.
Creating config file /tmp/_etc_exports with new version
Setting up libpython3.11:amd64 (3.11.2-6+deb12u5) ...
Setting up avahi-daemon (0.8-10+deb12u1) ...
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-28-amd64
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-6.1.0-28-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.36-9+deb12u9) ...
Processing triggers for systemd (252.33-1~deb12u1) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Errors were encountered while processing:
linux-image-6.1.0-29-amd64
linux-image-amd64
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
Display More
I tried to solve this using the "apt-get -f install" command, but I also got an error.
root@omv420:~# apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
linux-image-6.1.0-27-amd64
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.142+deb12u1) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-6.1.0-29-amd64 (6.1.123-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-29-amd64
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-6.1.0-29-amd64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-29-amd64 (--configure):
installed linux-image-6.1.0-29-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-amd64:
linux-image-amd64 depends on linux-image-6.1.0-29-amd64 (= 6.1.123-1); however:
Package linux-image-6.1.0-29-amd64 is not configured yet.
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-28-amd64
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-6.1.0-28-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-6.1.0-29-amd64
linux-image-amd64
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
Display More
Then I uninstalled the Flash 7.1 plugin
root@omv420:~# apt remove openmediavault-flashmemory
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
linux-image-6.1.0-27-amd64
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
openmediavault-flashmemory
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 512 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 49513 files and directories currently installed.)
Removing openmediavault-flashmemory (7.1) ...
zram-config stop 2025-01-11-19:32:01-EET
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
/usr/sbin/zram-config: line 163: echo: write error: Device or resource busy
Setting up initramfs-tools (0.142+deb12u1) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-6.1.0-29-amd64 (6.1.123-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-29-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-29-amd64
Found initrd image: /boot/initrd.img-6.1.0-29-amd64
Found linux image: /boot/vmlinuz-6.1.0-28-amd64
Found initrd image: /boot/initrd.img-6.1.0-28-amd64
Found linux image: /boot/vmlinuz-6.1.0-27-amd64
Found initrd image: /boot/initrd.img-6.1.0-27-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Setting up linux-image-amd64 (6.1.123-1) ...
Processing triggers for openmediavault (7.5.0-1) ...
Restarting engine daemon ...
Updating workbench configuration files ...
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-29-amd64
Display More
After removing the plugin, the "apt-get -f install" command worked without errors
root@omv420:~# apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
linux-image-6.1.0-27-amd64
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
By the way, I don't see any problems with mail with the 7.1 plugin installed. It worked for a day and during all this time I received all the letters. Now, after the update, I have installed the 7.1 plugin again.
Your problem (and mine) was caused by /var/tmp being too small. 250M/750M is working for me. Still trying to figure out what a good size is. Unfortunately, you installed the update before the changed plugin which will change /var/tmp to 250M
You didn't want to post all the output?
My bad! Here you go...
ii folder2ram 0.4.0 all script-based utility to manage tmpfs folders
ii openmediavault 7.5.0-1 all openmediavault - The open network attached storage solution
ii openmediavault-cputemp 7.0.2 all cpu temperature plugin for openmediavault
ii openmediavault-fail2ban 7.0.1 all OpenMediaVault Fail2ban plugin
ii openmediavault-flashmemory 7.1 all zram-config plugin for openmediavault
ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
ii openmediavault-mergerfs 7.0.5 all mergerfs plugin for openmediavault.
ii openmediavault-omvextrasorg 7.0 all OMV-Extras.org Package Repositories for OpenMediaVault
I uninstalled the original flashmemory plugin, rebooted, and installed the latest test version. Output looks the same:
ii folder2ram 0.4.0 all script-based utility to manage tmpfs folders
ii openmediavault 7.5.0-1 all openmediavault - The open network attached storage solution
ii openmediavault-cputemp 7.0.2 all cpu temperature plugin for openmediavault
ii openmediavault-fail2ban 7.0.1 all OpenMediaVault Fail2ban plugin
ii openmediavault-flashmemory 7.1 all zram-config plugin for openmediavault
ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
ii openmediavault-mergerfs 7.0.5 all mergerfs plugin for openmediavault.
ii openmediavault-omvextrasorg 7.0 all OMV-Extras.org Package Repositories for OpenMediaVault
Everything seems to be working fine.
I did just upload a significant change in the 7.1 plugin. It adds a datatable for each zram directory. This will allow people to edit the size of the mounts, add or remove mounts, and remove swap if they don't need it.
That's awesome!
Don’t have an account yet? Register yourself now and be a part of our community!