Bug 489640
Summary: | Filesystem on encrypted PV not fscked? | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kevin R. Page <redhat-bugzilla> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | notting, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-11 03:26:07 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: |
Description
Kevin R. Page
2009-03-11 02:56:44 UTC
Ok, so having worked out I needed to search around "upstart", I found I needed to touch /forcefsck rather than /.autofsck these days. This forced a fsck on reboot, which relieves me of my major worry - that the FS might never be checked, even if it needed it. (I'll put the gnome panel weirdness after an unclean reboot down to general fragility, rather than FS errors, which I can cope with less nervously ;) ) |