| 2006-09-30 13:44:08 |
Henk Koster |
bug |
|
|
added bug |
| 2006-10-04 07:46:30 |
towsonu2003 |
None: statusexplanation |
|
|
|
| 2006-10-04 07:46:49 |
towsonu2003 |
e2fsprogs: status |
Unconfirmed |
Confirmed |
|
| 2006-10-10 20:41:50 |
Mateusz Drożdżyński |
e2fsprogs: importance |
Undecided |
Medium |
|
| 2006-10-21 03:48:07 |
Tom R |
bug |
|
|
added attachment 'edgy-20061021-1.png' (chart) |
| 2007-03-01 00:56:51 |
Brian Murray |
e2fsprogs: assignee |
|
brian-murray |
|
| 2007-03-01 00:56:51 |
Brian Murray |
e2fsprogs: statusexplanation |
|
Thanks for taking the time to report this bug and helping to make Ubuntu better. When fsck is run it logs to /var/log/fsck/checkfs and /var/log/fsck/checkroot. Could you please add those files to your bug report? Thanks in advance. |
|
| 2007-03-01 01:19:05 |
humandoing |
bug |
|
|
added attachment 'checkroot' (fsck output (checkroot) - Daniel Wintschel) |
| 2007-03-01 01:19:58 |
humandoing |
bug |
|
|
added attachment 'checkfs' (fsck output (checkfs) - Daniel Wintschel) |
| 2007-03-01 21:44:17 |
Tollef Fog Heen |
e2fsprogs: statusexplanation |
Thanks for taking the time to report this bug and helping to make Ubuntu better. When fsck is run it logs to /var/log/fsck/checkfs and /var/log/fsck/checkroot. Could you please add those files to your bug report? Thanks in advance. |
Milestoning for beta to make sure this doesn't fall off the radar.
|
|
| 2007-03-08 15:30:25 |
Scott James Remnant (Canonical) |
e2fsprogs: assignee |
brian-murray |
mvo |
|
| 2007-03-08 15:30:25 |
Scott James Remnant (Canonical) |
e2fsprogs: statusexplanation |
Milestoning for beta to make sure this doesn't fall off the radar.
|
Assigned to mvo; please investigate this. Possibilities are that it's caused by faulty hardware clocks, and somehow it's not being set correctly (by the udev 85-hwclock.rules).
Or maybe it's something even weirder. |
|
| 2007-03-12 11:40:08 |
Michael Vogt |
e2fsprogs: status |
Confirmed |
Needs Info |
|
| 2007-03-12 11:40:08 |
Michael Vogt |
e2fsprogs: statusexplanation |
Assigned to mvo; please investigate this. Possibilities are that it's caused by faulty hardware clocks, and somehow it's not being set correctly (by the udev 85-hwclock.rules).
Or maybe it's something even weirder. |
|
|
| 2007-03-13 01:15:09 |
humandoing |
bug |
|
|
added attachment 'edgy-20070313-1.png' (bootchart from Daniel Wintschel) |
| 2007-03-13 01:23:46 |
humandoing |
bug |
|
|
added attachment 'tune2fs_output.txt' (output of tune2fs -l /dev/hda1) |
| 2007-03-13 01:26:17 |
humandoing |
bug |
|
|
added attachment 'udev.gz' (gzipped /var/log/udev) |
| 2007-03-27 14:10:46 |
Tollef Fog Heen |
e2fsprogs: statusexplanation |
|
Bringing milestone forward |
|
| 2007-06-18 21:30:40 |
Brian Murray |
bug |
|
|
added subscriber Canonical Distro QA |
| 2007-06-26 11:22:54 |
Henrik Nilsen Omma |
bug |
|
|
added subscriber Canonical Ubuntu QA Team |
| 2007-06-29 19:04:45 |
Henrik Nilsen Omma |
e2fsprogs: statusexplanation |
|
We are checking the file system after 180 days by default and this errors seems to occur for people who are ahead of GMT by a few hours (and people with wasted batteries probably).
Could we not simply fix this by adding 12+ hours to the time variable in the code that checks against last fsck? In reality that would cause a check every 179.5 days, but who's counting? :)
The last comment by tillicollaps3 describes a work-around that suggests this should work.
|
|
| 2007-07-17 06:17:29 |
Sarah Kowalik |
e2fsprogs: statusexplanation |
We are checking the file system after 180 days by default and this errors seems to occur for people who are ahead of GMT by a few hours (and people with wasted batteries probably).
Could we not simply fix this by adding 12+ hours to the time variable in the code that checks against last fsck? In reality that would cause a check every 179.5 days, but who's counting? :)
The last comment by tillicollaps3 describes a work-around that suggests this should work.
|
|
|
| 2007-08-09 00:24:18 |
Martin Pitt |
title |
Edgy Beta -- fsck on every (re)boot |
fsck on every (re)boot |
|
| 2007-08-14 17:22:55 |
dahas |
bug |
|
|
added attachment 'edgy-20070814-3.png' (This is bootchart with all running services) |
| 2007-09-04 21:04:12 |
Scott James Remnant (Canonical) |
e2fsprogs: assignee |
mvo |
ijackson |
|
| 2007-09-05 22:05:59 |
Stéphane Graber |
description |
I'm running a fresh install of Edgy Beta, 2.6.17-10-generic kernel for x86_64 (amd64), using /dev/sda1 ext2 mounted on /boot and /dev/sda6 jfs mounted on /. Both partitions are checked with fsck on every (re)boot, (and invariably found to be clean. This happens both when booting regularly or (repeatedly) in single-user mode.
FWIW, usplash fails on my AMD64 box, even with the latest update on 30 Sept/06. There is also sometimes during the boot process a message that the configuration of usb 1-1... cannot be read (freely paraphrased).
Finally, I also run 64-bit Dapper (2.6.15 kernel) and 64-bit Gentoo (2.6.17 kernel) in different partitions on the same computer -- never any problem with hardware or splash. |
I'm running a fresh install of Edgy Beta, 2.6.17-10-generic kernel for x86_64 (amd64), using /dev/sda1 ext2 mounted on /boot and /dev/sda6 jfs mounted on /. Both partitions are checked with fsck on every (re)boot, (and invariably found to be clean. This happens both when booting regularly or (repeatedly) in single-user mode.
FWIW, usplash fails on my AMD64 box, even with the latest update on 30 Sept/06. There is also sometimes during the boot process a message that the configuration of usb 1-1... cannot be read (freely paraphrased).
Finally, I also run 64-bit Dapper (2.6.15 kernel) and 64-bit Gentoo (2.6.17 kernel) in different partitions on the same computer -- never any problem with hardware or splash. |
|
| 2007-09-12 06:59:37 |
Sitsofe Wheeler |
e2fsprogs: status |
Incomplete |
New |
|
| 2007-10-02 14:10:10 |
LaMont Jones |
bug |
|
|
added subscriber Ubuntu Release Team |
| 2007-10-23 16:02:54 |
Ian Jackson |
e2fsprogs: assignee |
ijackson |
|
|
| 2007-10-23 16:03:13 |
Ian Jackson |
e2fsprogs: assignee |
ijackson |
|
|
| 2008-02-26 09:29:16 |
Martin Pitt |
e2fsprogs: importance |
Medium |
High |
|
| 2008-02-26 09:29:16 |
Martin Pitt |
e2fsprogs: milestone |
|
ubuntu-8.04-beta |
|
| 2008-03-20 20:44:20 |
Steve Langasek |
e2fsprogs: milestone |
ubuntu-8.04-beta |
ubuntu-8.04 |
|
| 2008-03-27 21:46:05 |
Steve Langasek |
e2fsprogs: status |
New |
Fix Released |
|
| 2008-03-27 23:54:39 |
Wenzhuo Zhang |
e2fsprogs: status |
Fix Released |
In Progress |
|
| 2008-03-28 01:03:35 |
Steve Langasek |
e2fsprogs: status |
In Progress |
Fix Released |
|
| 2008-09-06 17:27:25 |
Steve Langasek |
e2fsprogs: status |
New |
Won't Fix |
|
| 2008-09-06 17:27:25 |
Steve Langasek |
e2fsprogs: statusexplanation |
|
This bug has been nominated for gutsy, but it seems unlikely that we're going to see any SRU activity for it given that there's been a subsequent Ubuntu release since then. Marking 'wontfix'. |
|
| 2009-09-06 14:06:41 |
Caracuri |
nominated for series |
|
Ubuntu Karmic |
|
| 2012-03-31 14:52:50 |
Christian Diefenbach |
bug |
|
|
added subscriber Christian D. |
| 2012-03-31 14:54:12 |
Christian Diefenbach |
removed subscriber Christian D. |
|
|
|
