FS#35593 - [systemd] uninterruptible fsck

Attached to Project: Arch Linux
Opened by jozef riha (jose1711) - Saturday, 01 June 2013, 20:39 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 01 June 2013, 21:56 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
i was very much used to have an option to abort filesystem check of large filesystems during boot process if i had to (did not have time to wait 20+ minutes). it seems that implementing of systemd took away this feature and ^c is now completely ignored

Additional info:
* systemd 204-2

Steps to reproduce:
* schedule fsck (e. g. using tune2fs) on the following reboot
* reboot
* try to skip the check
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 01 June 2013, 21:56 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream known issue. Use an automoubt or disable checking if you don't want to wait on fsck.
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 01 June 2013, 21:15 GMT
  • Field changed: Summary (uninterruptible fsck since systemd → [systemd] uninterruptible fsck)
  • Field changed: Status (Unconfirmed → Waiting on Response)
  • Field changed: Category (Packages: Core → Upstream Bugs)
  • Task assigned to Dave Reisner (falconindy), Tom Gundersen (tomegun)
Nothing to do here, upstream issue.
http://cgit.freedesktop.org/systemd/systemd/tree/TODO : * There's currently no way to cancel fsck (used to be possible via C-c or c on the console)

Just disable filesystem check for now.

Loading...