Felix Miata wrote:
On 2014-01-21 14:30 (GMT-0800) Linda Walsh composed:
Perhaps it isn't the fsck step at all, but perhaps output is being buffered somewhere and the problem is in one of the steps immediately after the fsck, but isn't getting written to the log or console?
It seems to have nothing to do with the problem except for producing inexplicable entries in blame output. No fscking is apparent while watching boot proceed. Stripping all fstab lines except for / has no impact on boot time, and affects only 13.2, not 13.1, on the very same systems using the very same partitions and filesystems.
What comes after fsck?... On my system it switches from runlevel-S to runlevel-3 and starts bringing up services. It also happens to be the point in my startup log that 'the kernel log daemon terminates and boot logging starts'... I've noticed some output overlaps at times between the boot log and the kernel log , but in my case, the kernel log catches all of the file-system mounts because the normal boot logging doesn't come up until the file systems are mounted. So... maybe you are seeing kernel log type output that catches the end of the fsck's, and ... (ignorance on my part here) -- is it journald that comes up to take over logging? Maybe it isn't logging anything to disk for some period of time during boot in order to speed up boot? i.e. writing a log to disk while loading lots of things, might be thought to be counter-productive if someone was trying to optimize disk reads during boot, but that's guessing on my part... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org