Similarly, you can't unmount a filesystem that has any file open (or similar uses of files such as a process having its current directory there, a running executable, etc.). You normally can't remount a filesystem as read-only if processes have a file on it that's open for writing, or if it contains a file that's deleted but still open. Is there any better way I can force a single disk partition to read-only and sustain it in that state for half an hour and bring it back to read-write mode without causing any reboot in the process? I don't want the machine to reboot itself and need to keep the disk in read-only mode for 30+ minutes. Not sure what is causing this reboot yet. Some machines are rebooting immediately once this command is executed. But after 20-30 minutes the machine is rebooting itself. Issue: This will make all the disk partitions read-only (although device is busy). Used magic sysrq key, like below echo u > /proc/sysrq-trigger I want to simulate the disk suddenly going read-only when the processes are still using it. I don't want to kill the processes using the disk. Issue: This gave device busy error as some processes were using the partition. Mount -o remount,ro (partition-identifier) (mount-point) -t (filesystem) test-binary = /rofscheck.I want to force a disk partition to read only mode and keep it read-only for more than 30 minutes. Grep -q ' ro' /proc/mounts > /dev/null 2>&1 || exit 0 What i expect is to check if uptime if less then a day then it should not reboot even though any mount point is cat /rofscheck.sh #!/bin/bash
This works but it continuously reboot if script return exit 1 due to any mount point is still readonly. Tried: I tried to write a script as below which will get monitored by watchdog. Question: Is there any mechanism to reboot the appliance if it comes to readonly mounted state.
Reason is clear as mentioned in fstab on errors=remount-ro. Problem: We generally face a problem where ubuntu os gets mounted readonly.
0 kommentar(er)
