Posts by votdev

    OK, did some testing and the .recycle dir is only populated with a file if it is deleted AND the recycle checkbox is checked.

    There are more questions. Where is the file opened, in a global share or a specific home dir? Where is the unencryped archive located after you've opened it? In the shared folder or the home share?

    Is it possible that you have enabled recycle bin and the behaviour you see is the result of your archive tool? Maybe it somehow duplicates the file for decryption and deletes it afterwards.

    If there is a copy of your previously opened archive in the .recycle dir, then you MUST have enabled the recycle bin feature. Samba will surely not create this dir on its own.

    Hmmm, strange behaviour of Samba. To me the OMV generated smb.conf looks ok, no recycle bin is configured when the checkbox is not set. So this must be something internal to Samba. Have you checked the issue tracker of the upstream Samba project? Please note that OMV is only generating the configuration of the services it provides, everything else is out of the control of the OMV project. Bugs of the services used by OMV have to be reported at Debian or the upstream project itself.

    any news on this?

    No. It will be done when it is ready. There is currently no big benefit in using Debian 12. One show stopper is Salt which needs to be adapted to Debian 12 before, otherwise you'll get spammed with Python warnings in systemd journal. And when Salt 3007 will be released is in the stars.

    I think I can't do anything about it

    That's true, first come, first served; that's how the kernel handles this for device names. That's why OMV is using predictable device names wherever possible. If the system (more precisely Udev) does not provide them, OMV can't do anything to prevent the problems that arise of this device name behaviour.

    I forgot my OMV was visible on the internet with swag, so I was curious I tried a lot of time to log in with different wrong passwords, but neither OMV or fail2bafail2ban from swag prevent me to try to log in even after putting maybe 10 wrong passwords in a minute, anything to modify to prevent this behavior?

    I do not know how fail2ban is implemented and which services are affected (because i do not use it), but OMV is using pam_faillock to lock users automatically out for all services that rely on the Linux PAM infrastructure (which includes OMV WebUI, SSH, FTP, ...).

    Is there any downside to using the sharerootfs plugin?

    No, except that you have to take care about your user data if you need to reinstall the OS. If you reinstall Debian/OMV/the OS image your user data is lost if you do not backup it before. That is the reason why OMV strictly separates OS and user data disks.

    The dev/mmcblk1 device contains your root file system. Because of that OMV does not allow you to mount it. First it is already mounted and second reason is OMV does not use this file system with reason to separate user data from OS data.

    If you want to overrule this behaviour, you have to install the openmediavault-sharerootfs plugin.

    I'm a little bit confused. The screenshot in the first post absolutely does not match the output of blkid in your last post.

    Could you please post

    # ls -alh /dev/mmc*