|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast Module for Adjusting ext2/ext3 File System Checks | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Philippe Landau <lists> |
| Component: | YaST2 | Assignee: | Michael Loeffler <michl> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | carlosflange, lists |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Philippe Landau
2008-02-17 13:02:00 UTC
To be fair, the comment above about the kernel people was written by Carlos Robinson. My comment about warning of an impending file system check and offering the option to opt-out would be better handled at boot time, as suggest in bug 344271. I would suggest to Phillipe to rename this report to: Yast Module for Adjusting ext2/ext3 File System Checks because the suggestion is not really about repairing the file system and it only applies to ext2/ext3 (unless there another tools like tune2fs for other file systems). More specifically, I would like to see a Yast module that allows us to set the interval or count between checks for each partition, since smaller partitions may be handled different from larger partitions. The help text on the left should warn against disabling check completely and the values could be preset to the current 2 months or 500 count standard. Changed title in agreement with the reporter. An off-line discussion brought to light the need to add a clarification about the check and repair process to the left hand help panel. Specifically, explain that the checks are made during the boot process and that in case of error that cannot be fixed automatically, there is a repair tool that the user should use. This feature request seems to cover several things. Some of them might have to be implemented on the file system / kernel (or kernel module) level, some others (front-end for tune2fs) could be done in an existing YaST2 module (yast2-storage), some others would have to go to the base system where fsck is handled. Michl, please decide and move to FATE if appropriate. It's covered through Fate #302118: switch off paranoid ext3 fsck, the outcome is that file system check is off per default but can be enabled by checking a check box. Fate 302118 is restricted access, but it sounds good from your description. Can you tell us, Michael, if it is a Yast2 module and if the suggested clarification (last sentences in comments #1 and #2 above) is being added to the left-hand help panel? won't fix |