Public bug reported:
Binary package hint: e2fsprogs
When you are East of UTC, and your hardware clock is in localtime not
UTC, and you have to force power down, fsck fails on boot because the
last write time is in the future.
This is caused by a bug in the ext3/4 filesystem code in kernel, where
it updates the superblock last write time from the system clock after
replaying the journal - but the system clock contains localtime not UTC
since we haven't had an opportunity to correct it yet.
Ted Tso (ext3/4 upstream) is working on a fix to not write this time
when the filesystem is read-only
** Affects: e2fsprogs (Ubuntu)
Importance: Critical
Status: Triaged
** Affects: linux (Ubuntu)
Importance: Critical
Status: Triaged
** Affects: e2fsprogs (Ubuntu Karmic)
Importance: Critical
Status: Triaged
** Affects: linux (Ubuntu Karmic)
Importance: Critical
Status: Triaged
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Karmic)
Milestone: None => karmic-alpha-6
** Changed in: e2fsprogs (Ubuntu Karmic)
Importance: Undecided => Critical
** Changed in: e2fsprogs (Ubuntu Karmic)
Status: New => Triaged
** Changed in: linux (Ubuntu Karmic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Karmic)
Status: New => Triaged
--
fsck says last write time in future
https://bugs.launchpad.net/bugs/427822
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
