Bug 114335 - unbidden fsck on crypto-partition while installation
Summary: unbidden fsck on crypto-partition while installation
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 3
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 07:12 UTC by Christian Boltz
Modified: 2005-08-31 08:17 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2005-08-31 07:12:33 UTC 
When mounting my encrypted /home partition while installation, YaST does an 
unbidden fsck on it. 
 
Besides taking some time, I consider this possibly dangerous - what if 
somebody has entered a wrong password or /etc/cryptotab from the "old" system 
contains a wrong encryption type (remember the problem in 9.3!)? Will this 
fsck damage the filesystem in this case? 
 
You can find the y2logs at 
https://bugzilla.novell.com/attachment.cgi?id=48265
Comment 1 Thomas Fehr 2005-08-31 08:17:06 UTC 
The fsck should happen if you use YaST2 to integrate the encrypted fs into
your system. The fsck is needed to determine which encryption type is used.
Yes, it needs some time but it makes the detection process much more reliable.

The options used for the fsck calls are so that the fsck does not try to repair
anything but only returns if the fs is clean, so there should not be any
possible damage by these calls.