Bug 113605

Summary:	disk usage on windows partition is 0 during installation
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	peter czanik <peter>
Component:	Installation	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 3
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 logs

Description peter czanik 2005-08-28 08:44:21 UTC

During installation, YaST incorrectly displays zero disk usage for windows
partitions. The partition size was displayed correctly. It's a pretty disturbing
feeling...

Comment 1 Arvin Schnell 2005-08-29 15:50:45 UTC

Please provide YaST2 log of installation, see:
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST

Comment 2 peter czanik 2005-08-29 17:47:57 UTC

Created attachment 48049 [details]
YaST2 logs

Comment 3 Thomas Fehr 2005-09-05 08:01:26 UTC

yast2-storage does not provide any information about disk usage.
AFAIK this data is determined in module SpaceCalculation.ycp, Jiri could you 
have a look.

Comment 4 Jiri Srain 2005-09-09 09:18:45 UTC

Hmm, it seems to me that "used" is always initialized as 0 during installation 
(see SpaceCalculation::get_partition_info () function). So I guess that this 
bug has been there for several releases. 
 
Arvin, do you remember how it was supposed to work?

Comment 5 Arvin Schnell 2005-09-09 14:27:15 UTC

No, I can't remember.  But after a short look I see that in EvaluateFreeSpace
the .run.df agent is used.  Without actually doing an installation I can't
say more.

Comment 6 Thomas Fehr 2005-09-12 09:40:28 UTC

Mayb this is caused because YaST2 mount ntfs partitions readonly.
No idea what .run.df does in this case.

I would think it would be best to simply remove such partitions from the
display during package installation. Since they are mounted readonly one
cannot install anything on them anyway.

Comment 7 Jiri Srain 2005-10-04 12:20:56 UTC

The problem is somewhere else: There are two ways to determine the space on 
the disks. One is EvaluateFreeSpace, and the other one is get_partition_info. 
The later is used only during fresh installation, and supposes all partitions 
will be formatted (which is of course wrong).

Comment 8 Jiri Srain 2005-10-04 14:52:32 UTC

Fixed for 10.1.