Bug 394031
| Summary: | Ambiguous text in tune2fs man page | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fred New <fred.new2911> |
| Component: | e2fsprogs | Assignee: | Oliver Falk <oliver> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | kzak, oliver |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-11-21 12:37:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
(In reply to comment #0) > Description of problem: > > Near the top of the man page, we see the following text: > > "-c max-mount-counts > Adjust the number of mounts after which the filesystem will be > checked by e2fsck(8). If max-mount-counts is 0 or -1, the num- > ber of times the filesystem is mounted will be disregarded by > e2fsck(8) and the kernel." > > If my max-mount-counts is 0 or -1, will the system check my filesystem at the > next boot, or not? Is there a default action defined for when e2fsck and the > kernel disregard the number of filesystem mounts? Well, you should have better asked that on the m/l instead of opening bz. However. I've never used -1, but for 0 I know, the mount-count is ignored and the system will never do a fsck - if the system is shut down cleanly. If the system crashes, that's a total other story... However. If you want to force a filesystem check at some reboot, you usually should touch /forcefsck. I never used that but I guess it will work... :-) The idea here was to get the text fixed, not to just get the answer to my questions. Although, filing this bug in the upstream bugzilla might have been more useful. Of course. If you want such a change, you better file a bug upstream. Although I think the man-page is quite clear... Yes, I see what the man page means now. For me it is unclear because when I use "dumpe2fs -h /dev/...", I see <snip> Mount count: 10 Maximum mount count: -1 <snip> To me, the tune2fs man page says that it will disregard the 10 (mount count) and substitute something like -99999 or 99999. But what it really means is that "the mount count test won't be used to determine whether e2fsck will be run." Yes. That does it mean. :-) |
Description of problem: Near the top of the man page, we see the following text: "-c max-mount-counts Adjust the number of mounts after which the filesystem will be checked by e2fsck(8). If max-mount-counts is 0 or -1, the num- ber of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel." If my max-mount-counts is 0 or -1, will the system check my filesystem at the next boot, or not? Is there a default action defined for when e2fsck and the kernel disregard the number of filesystem mounts? Version-Release number of selected component (if applicable): e2fsprogs-1.40.2-10.fc8 (But I see similar text on RHEL systems.)