Bulldog, this is due to Ubuntu having buggy init scripts, and not setting the time correctly before running e2fsck. For some number of strange reasons I haven't been able to get Ubuntu staff to deal with this problem correclty, so starting with e2fsprogs 1.40.3, the debian/rules files have been set up to work around the problem using an /etc/e2fsck.conf script:
Bulldog, this is due to Ubuntu having buggy init scripts, and not setting the time correctly before running e2fsck. For some number of strange reasons I haven't been able to get Ubuntu staff to deal with this problem correclty, so starting with e2fsprogs 1.40.3, the debian/rules files have been set up to work around the problem using an /etc/e2fsck.conf script:
[options]
buggy_ init_scripts = 1