Bug 1167202
Summary: | fsck Next check after: does not work properly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Leo Dogterom <dogterom> |
Component: | e2fsprogs | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | dogterom, esandeen, jonathan, josef, kzak, oliver |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-07 19:49:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leo Dogterom
2014-11-24 08:14:26 UTC
What version of e2fsprogs? e2fsprogs-1.42.7-2.fc19.x86_64 It seems to work here, how have you determined that it doesn't work? # dumpe2fs -h pastdate.img | grep check Last checked: Thu Nov 20 10:19:22 2014 Next check after: Fri Nov 21 10:19:22 2014 # date Mon Nov 24 10:21:09 CST 2014 # e2fsck/e2fsck -p pastdate.img pastdate.img has gone 4 days without being checked, check forced. pastdate.img: 11/32768 files (0.0% non-contiguous), 9787/131072 blocks # e2fsck/e2fsck -V e2fsck 1.42.7 (21-Jan-2013) Using EXT2FS Library version 1.42.7, 21-Jan-2013 -Eric Or if you prefer, w/o -p: # e2fsck/e2fsck pastdate.img e2fsck 1.42.7 (21-Jan-2013) pastdate.img has gone 4 days without being checked, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information pastdate.img: 11/32768 files (0.0% non-contiguous), 9787/131072 blocks Re: It seems to work here, how have you determined that it doesn't work? [root@xxxxxx ~]# dumpe2fs -h /dev/sdb1|grep check dumpe2fs 1.42.7 (21-Jan-2013) Last checked: Wed Nov 19 12:35:27 2014 Next check after: Thu Nov 20 12:35:27 2014 [root@bhw325 ~]# date Mon Nov 24 16:46:19 GMT 2014 [root@xxxxxx ~]# e2fsck -p /dev/sdb1 nobackup: clean, 573973/91578368 files, 326120949/366284288 blocks [root@xxxxxx ~]# dumpe2fs -h /dev/sdb1|grep check dumpe2fs 1.42.7 (21-Jan-2013) Last checked: Wed Nov 19 12:35:27 2014 Next check after: Thu Nov 20 12:35:27 2014 [root@xxxxxx ~]# Well that's odd, isn't it. Let me actually get a proper F19 box provisioned and take a look. -Eric Oh, ok - hohum, it's this in /etc/e2fsck.conf, which I'd forgotten about. # cat /etc/e2fsck.conf [options] # This will prevent e2fsck from stopping boot just because the clock is wrong broken_system_clock = 1 I thought that was smart enough to only ignore seriously mangled system times. I'll have to go back & remember why we had this, and most likely remove it. Perhaps accept_time_fudge would be better middle ground, though I'll have to re-remember how this is all supposed to work. For now, just comment that line out and you'll get the behavior you expect. -Eric Hello Eric Commenting out the line did the job. The filesystem check works now. Thanks Leo This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Still need to fix this, but it's also a dup of another bug, so doing that. *** This bug has been marked as a duplicate of bug 963283 *** |