>I still dont get the proper answer at this simple question on each bug reports.
>Why settings made by tune2fs isnt check by fsck.

E2fsck is checking the superblock settings made by tune2fs.  However, in
order to perform the check based on times since last fsck time, e2fsck
requires that the system clock be set correctly.  With current buggy
Debian/Ubuntu boot scripts, this isn't happening.

I could work around the problem by adding a config option to
/etc/e2fsck.conf

[work-around-buggy-Ubuntu-boot-scripts]
       time-offset = 43200

Which would tell e2fsck to subtract 43,200 seconds from the time
returned by time(0), to work around the fact that Ubuntu is screwing up
the system clock in the early boot cycle due to not correctly handling
the time zone correctly.   But otherwise, this is not a problem to
solved by e2fsck, but by the buggy Debian/Ubuntu boot scripts that can't
be bothered to have the time set correctly when e2fsck is run.

-- 
fsck on every (re)boot
https://bugs.launchpad.net/bugs/63175
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to