Hide Forgot
Description of problem: I have multiple partitions (ext3) on the same hard drive set up as automount points. When one of them has reached its maximum mount count it is checked. The other partitions have to wait for their journals to be replayed until the check of the first partition is finished. Version-Release number of selected component (if applicable): systemd-26-2.fc15 How reproducible: Tried on two different PCs, both showed this Steps to Reproduce: 1. configure two partitions on the same hard drive as automount points 2. have the first of the two partitions exceed its maximum mount count 3. reboot Actual results: Both fscks run with the second one apparently waiting for the first one to finish. Only after that both partitions are mounted. Expected results: The second partition should immediately do its journal replay and not wait for the fsck of the first partition (unless it also has to do a complete check).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
still a problem with systemd-37-3.fc16
So what we want asynchronous fsck as in all fsck against all drives/partitions are started at the same time?
(In reply to comment #3) > So what we want asynchronous fsck as in all fsck against all drives/partitions > are started at the same time? That would likely have a horrible performance when more than one fsck is run on the same drive. My suggestion would be to do all journal replays first, and only after that do the full checks if needed (one per drive at a time). That means all partitions which do not need a full check can be accessed while the full checks are still running.
Moving this to assigned since this is a real problem that needs to be solved. Given that this is not a change to previous behaviour ( regression ) thus is not the highest priority on the list to fix. Probably will take sometime coming up with a future proof solution to this problem and properly implement that solution in all the right bits across the relevant components ( think maybe F18+ )
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.