Did you clear the cache using omv-firstaid as well?
System Disk is full
-
-
Did you clear the cache using omv-firstaid as well?
THANK YOU THANK YOU THANK YOU!
So I just want to understand why, so its doesn't happen again. If using urBackup, surely if it can not find the mounted backup drive, urbackup should wait rather than write to the system disk?
-
Maybe you should ask this in the UrBackup forum
How did you specify the path? With /sharedfolders/.... or with /srv/dev-disk......?
You should use the srv version, but not sure if this has an impact on the behavior you experienced. -
-
i've used the srv version.
i have asked other questions on urbackup forum but never get any replies, its not as good as OMV forums!
-
its not as good as OMV forums!
So let's challenge the OMV forum; Does anybody have an answer?
-
While I wait for that answer, I'm now getting this error message when trying to apply config changes:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run avahi 2>&1' with exit code '100': ERROR: The state 'avahi' does not exist
-
-
While I wait for that answer, I'm now getting this error message when trying to apply config changes:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run avahi 2>&1' with exit code '100': ERROR: The state 'avahi' does not exist
This looks like a faulty installation.
Try to reinstall with
# apt-get install —reinstall openmediavault
-
This looks like a faulty installation.
Try to reinstall with# apt-get install —reinstall openmediavault
is this going to remove allof my settings etc by a new reinstall or will it just 'repair' whats damaged?
EDIT: It doesn't work anyway, says Unable to locate package -reinstall
-
There are two "-" in front of reinstall.
It is --reinstall not -reinstall
-
-
ok thanks macom - is this going to rewrite of my settings or does it kind of repair things?
-
I am quite sure that settings will persist.
-
Normally this is caused by a not available filesystem (incl. shared folders) which is the target of a backup/rsync/whatever job. So you might concentrate on looking into the /srv directory where all filesystems are mounted. If a filesystem is not mounted and a rsync job or something else is writing to a shared folder the data is written into thr root filesystem instead.
Your du command should have to the -x flag to not traverse other filesystems. That way, you will still see usage in /srv even in filesystems are mounted on the subdirectories.
sudo du -x -d1 -h / | sort -h
Thank you a lot. It was exactly this happening and you helped me figure out the problem in really much less time than it would have took! I now created a script that first tries to read a file that is ONLY in the mounted drive so that if it isnt, the rsync will not happen.
-
-
Thank you a lot. It was exactly this happening and you helped me figure out the problem in really much less time than it would have took! I now created a script that first tries to read a file that is ONLY in the mounted drive so that if it isnt, the rsync will not happen.
That is clever. Another option is to store the script on the remote server, and launch it using a cron-job (or a Scheduled Job) on the local server that also will run the script. Then the script itself is used to flag if the remote server is available.
An advanced extra option (that I haven't tried) is to create a "mirror script" in a subfolder to the mount point (when nothing is mounted) with the same path and name as the remote script. Then this local mirror script will be executed if the remote server is not mounted, rather than the remote script. For instance to mount the remote server and/or notify that it is not mounted.
When the share of the remote server is mounted then the "mirror" script is not visible and the normal "remote" script is executed.
-
Other option that should work:
Use mountpoint to check if the given directory is a mount point.
If the filesystem is not mounted, the directory will either not exist (normal case) or will not be a mountpoint.
-
Actually rsync in OMV should check if the filesystem is mounted. The code in /var/lib/openmediavault/cron.d/
has following:
Bashif ! omv_is_mounted "/srv/dev-disk-by-label-xxx/" ; then omv_error "Source storage device not mounted at </srv/dev-disk-by-label-xxx/>!" exit 1 fi
for source and target. BUT on my system (2x OMV5 and 1x OMV6) omv_is_mounted is not available.
votdev could you bring some light in this? Am I mistaken?EDIT: Got it, it is in the helper-function
Bash
Display More# omv_is_mounted <mountpoint> # Check if the given mount point is mounted. # @param mountpoint The mount point to check for # @return Return 0 if mounted, nonzero otherwise. omv_is_mounted() { if ! mountpoint -q "${1}"; then omv_debug "omv_is_mounted: Mount point '${1}' is not mounted" return 1 fi omv_debug "omv_is_mounted: Mount point '${1}' is mounted" return 0 }
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!