If an fsck is necessary during system boot, a message will be printed to that effect, but no progress information is displayed. (This is a regression from the old initscripts.) This produces an apparent stall at boot, and since the last messages printed before the (potentially very long) delay may not directly correspond to the fsck, it's confusing. (In fact, if there are many filesystems, or just other events which print status information around that time, the comment about fsck may scroll off the screen.)
*** Bug 694643 has been marked as a duplicate of this bug. ***
Also would be nice if the progress could be shown for automount points through systemadm and systemctl. For the root file system there appears no message at all if a fsck happens (at least if "rhgb quiet" is not removed from kernel command line). But that seems to be a problem with dracut and not systemd.
It is ATROCIOUSLY CONFUSING ! Especially after the previous behaviour where progress was made. At the very least _please_ put in a big fat message that fsck may be in progress, something like: ******* fsck in progress ******* It is about human psychology and managing expectations: -- The current message that fsck has started is easy to miss among the sea of other messages. -- An experienced user will think the system hanged (he would expect the progress bar otherwise), he won't see the fsck message because he has thinking filters in place that will "delete" the barely noticeable fsck message. -- An in-experienced user will think the system hangs (he won't be able to see the fsck message either because he will not look for it and will not understand the "gibberish" on the screen.) Regards.
So what can we do to help fix this bug? Waiting for /home that is on ext4 on lvm2 on crypto on raid5 to be fscked can take a while. Progress bar like we had needs to return.
(In reply to comment #4) > So what can we do to help fix this bug? Read the thread: http://lists.freedesktop.org/archives/systemd-devel/2011-April/002063.html Help review a proposed patch: http://lists.freedesktop.org/archives/systemd-devel/2011-June/002654.html
Why take development discussion outside of bugzilla to lists that we are not members of? By now you should know what I am, and what I want.
Oh, I thought the "we" in the question "what can we do to help fix this bug?" stood for "I or anyone else interested in this bug". Hence I answered with the links to the upstream mailing list where the development takes place and where help is actually needed to fix the bug. I hoped the links would be found relevant and useful. > By now you should know what I am, and what I want. Right, now I understand that the use of "we" in the question was in fact pluralis majestatis. Your Royal Highness, I apologize for not recognizing it earlier.
We as users. What can we test, choose, comment on? I won't go into the `joke`.
This appears to be fixed in the version of systemd that is now in F16 (for certain it is in systemd version 36-3, It may have been in an earlier version as well. It is a percentage completed display that shows up if a filesystem check is being done at boot, so at least the user isn't left staring at a blank screen wondering if the system is hung or not, or why it is just sitting there. I have had this to come up on my systems here several times now, and it does seem to be working correctly. Just commenting here to remind whomever that it is at least in the works,and seems to be working properly for me, so that this bug can be updated accordingly.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.