Thank You for the quick reply.
To answer your questions as best as possible . . .
#1. Are you sure you got the UUID's correct?
Yes. Cut and Pasted from fstab. An apparent reported bug in logd is
stopping me from getting a hard copy of the boot log to absolutely
confirm but the internal files are all the same UUIDs.
#2. Were the filesystems mounted at the time? Fsck won't work on a
mounted filesystem; in fact you should have gotten a Big Fat Warning,
No. At the beginning of the script I inserted a couple of
umount commands with an EXIT on problems.
#3. Is it checking your filesystem after every boot?
Yes. It is echoed to the screen.
#4. And are you paying attention to *which* filesystem it is checking.
Yes. All the filesystems from my active partitions are checked on boot.
OR the information is echoed to the screen. I assume that it is being
checked.
#5. Are you sure it is checking the filesystems that you just checked
by hand?
Yes. As per the screen echoes.
#6. Please check using dumpe2fs -h /dev/hdb1, and note especially these
fields:
Yours:
Last mount time: Fri Jul 6 01:51:48 2007
Last write time: Fri Jul 6 01:51:48 2007
Mount count: 2
Maximum mount count: 22
Last checked: Thu Jul 5 22:56:02 2007
Check interval: 15552000 (6 months)
Next check after: Tue Jan 1 21:56:02 2008
Mine on start of testing:
Last mount time: Thu Jul 12 16:30:05 2007
Last write time: Thu Jul 12 16:30:37 2007
Mount count: 17
Maximum mount count: 22
Last checked: Wed Jul 11 18:48:34 2007
Check interval: 15552000 (6 months)
Next check after: Mon Jan 7 17:48:34 2008
Mine after several script runs:
Last mount time: Thu Jul 12 19:30:08 2007
Last write time: Thu Jul 12 19:30:22 2007
Mount count: 4
Maximum mount count: 22
Last checked: Thu Jul 12 17:52:30 2007
Check interval: 15552000 (6 months)
Next check after: Tue Jan 8 16:52:30 2008
#7. These should tell the tale about what is going on. It could be any
number of things, none of which would be an e2fsprogs bugs. The most
likeliest problem is that time is not correctly set at boot. See this bug here:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/43239
I am familiar with this bug report from my research before my bug
report. It is not the same. I always get the i.e. 34/35 or 20/21 messages. I
got the number when the tests are first run at first boot.
#8. But in any case, if you aren't checking the filesystems while they
are mounted, check using dumpe2fs after you do the check. That will
tell you the state of the filesystem, and whether or not e2fsck will do
a check when it runs. Note that if your system clock is not using GMT,
definitely take a look at the above referenced above.
I will incorporate the command 'dumpe2fs -h /dev/hdb1' into the
script and keep an eye on it. Outside influences could be at work here.
I will run my script everyday. This should ensure that a forced clean
never occurs.
Again, Thank You.
--
fsck not updating clean history
https://bugs.launchpad.net/bugs/125106
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
