Anybody know what has happened to the -F option on 12.1?
I know it might seem trivial but the ability to force an FSCK on restart was really useful. Is this just an oversight or are we expected to use some other methothod of forcing an FSCK on a reboot?
You tried switching to sysinitv from systemd?
On 2012-01-31 17:06, peteh wrote:
>
> Anybody know what has happened to the -F option on 12.1?
Since the manual doesn’t mention it, then it was removed. No idea why, but
the developer has changed.
> or are we expected
> to use some other methothod of forcing an FSCK on a reboot?
The manual in 11.4 says:
The -F flag means force fsck'. This only creates an advisory file /forcefsck which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide to run fsck(1) with a spe- cial force’ flag so that even properly unmounted file systems get
checked. After that, the boot process should
remove /forcefsck.
so try creating that file.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Carlos,
Thanks for that. Ive knocked together a quick script along the lines of
#!/bin/bash
/usr/bin/touch /forcefsck
/sbin/shutdown -r now
exit 0
I’ll call that from my root crontab. Not the most elegant but I’ve got time constraints, so pragmatism wins over elegance.
Pete
Now let us hope that the boot rc file keeps on testing it in future levels 
Henk,
tried that, but the I ran into
error loading shared libraries: libsystemd-daemon.so.0 cannot open shared object file: no such file or directory libsystemd-daemon.so.0
on reboot. I understand why the move to systemd (faster boot) but on a server I’m less concerned with speed and more concerned with FS integrity. (What was it I was told years ago now? An fsck a day keeps the restore away.:))
As I said to Carlos I’ve got a delivery to hit, so playing around is something I haven’t got the time for now. I can come to terms with systemd vs sysv when I get the time.
Pete