FS#1928 - Shutdown -F doesn't do anything

Attached to Project: Arch Linux
Opened by Glenn Matthys (RedShift) - Thursday, 23 December 2004, 08:19 GMT
Last edited by Judd Vinet (judd) - Wednesday, 29 December 2004, 17:40 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Hi,

When I do for example shutdown -r -F now, on reboot the filesystems aren't being checked. (-F means force fsck on reboot)
(application/octet-stream)    rc.sysinit.forcefsck.diff (0.7 KiB)
This task depends upon

Closed by  Judd Vinet (judd)
Sunday, 06 March 2005, 20:07 GMT
Reason for closing:  Implemented
Additional comments about closing:  added patch for next build
Comment by Judd Vinet (judd) - Wednesday, 29 December 2004, 17:47 GMT
Hmmm, I see what you mean here, but i'm not sure how to "fix" it.

In rc.sysinit, filesystems in /etc/fstab are checked on every bootup, so "forcing" an fsck doesn't really have any other effect.

Also, from shutdown(8):

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 special `force' flag so that even properly unmounted filesystems get checked. After that, the boot process should remove
/forcefsck.


But, according to fsck's manpage, there is no "force" flag.
Comment by Jaroslaw Swierczynski (swiergot) - Sunday, 06 March 2005, 17:34 GMT
It seems only fsck.{ext2,ext3,jfs} support -f option. fsck.reiserfs simply ignores it. Anyway, I submitted a patch that implements -F for filesystems that support it.
Comment by Damir Perisa (damir.perisa) - Sunday, 06 March 2005, 17:42 GMT
swiergot added a patch (attachement) to solve this

Loading...