FS#28947 - [initscripts] / fsck fails with invalid command line arguments in forcefsck mode
Attached to Project:
Arch Linux
Opened by Lucjan B (lucck) - Friday, 16 March 2012, 20:56 GMT
Last edited by Tom Gundersen (tomegun) - Saturday, 17 March 2012, 13:23 GMT
Opened by Lucjan B (lucck) - Friday, 16 March 2012, 20:56 GMT
Last edited by Tom Gundersen (tomegun) - Saturday, 17 March 2012, 13:23 GMT
|
Details
Description:
When i tried to force drive check in the next reboot by command shutdown -Fr now, after the reboot fsck failed because invalid commandline is passed to the fsck. Additional info: * versions: core/initscripts 2012.02.1-1 (base) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Tom Gundersen (tomegun)
Saturday, 17 March 2012, 13:23 GMT
Reason for closing: Fixed
Additional comments about closing: in git
Saturday, 17 March 2012, 13:23 GMT
Reason for closing: Fixed
Additional comments about closing: in git
UUID=def3b417-0241-4747-ad96-ccfcb9d94317 / ext4 defaults,noatime,discard 0 1
UUID=3daa59d8-d59d-4ca7-8be0-c6aec349d67e /home ext4 defaults 0 2
UUID=45e91c3a-21fd-46b4-b35c-d39d7a94802e swap swap defaults 0 0
The commanline passed to the fsck:
fsck -A -T -C -a -t nofs,nonfs4,nosmbfs,nocifs,nocodafs,noncpfs,noshfs,nofuse,nofuseblk,noglusterfs,nodavfs,nofuse.glusterfs,noopts=_netdev -- -f -M
Step to reproduce:
shutdown -Fr now
and after ther reboot fsck fails immediately, with error invalid commandline passed to the fsck
http://mailman.archlinux.org/pipermail/arch-projects/2012-March/002613.html
As far as I can tell this is triggered by the combination of the "fsck" hook in the initramfs and using forcefsck. Could you try editing /etc/rc.d/functions and swapping the last two arguments (${FORCEFSCK} ${IGNORE_MOUNTED}) to fsck in the function fsck_all.
If you can confirm that this fixes it I'll queue this for the next release (which should be very soon).
@falconindy: does mkinitcpio support forcefsck/fastboot?