Bug 158785

From which installation media do you install?

Factory in the true Beta8 state, hard disk via NFS.

I had booted initrd and linux from SL-OSS-factory/inst-source/boot/x86_64/loader/ and then used SL-OSS-factory/inst-source/ via NFS.

You can verify this at the df output above.

The captures were done with the "ssh textinstall" mode.

Could you, please, attach logs from the update? See http://en.opensuse.org/Bug_Reporting_FAQ#YaST for details...

/var/log/YaSt2 seems to be too big for Novell's bugzilla (> 10 MB).
So please tell me what to delete before sending:

 turion:0 00:12:51 /var/log # dir -rt YaST2/
total 166296
-rw-r--r--  1 root root 10503221 Mar 14 17:11 y2log-5
-rw-r--r--  1 root root 10485804 Mar 16 20:14 y2log-4
-rw-r--r--  1 root root 10485886 Mar 16 20:17 y2log-3
-rw-r--r--  1 root root      555 Mar 16 22:18 volume_info
-rw-r--r--  1 root root    20637 Mar 16 22:35 y2log.SuSEconfig
-rw-r--r--  1 root root     1477 Mar 16 22:38 macro_inst_cont.ycp
-rw-r--r--  1 root root     8367 Mar 16 22:38 y2start.log
-rw-r--r--  1 root root     3389 Mar 16 22:48 config_diff_2006_03_16.log
-rw-r--r--  1 root root   764738 Mar 16 23:13 y2logRPM
-rw-------  1 root root      451 Mar 16 23:15 y2log_bootloader
-rw-r--r--  1 root root      149 Mar 16 23:15 badlist
-rw-r--r--  1 root root        0 Mar 16 23:15 y2logMount
-rw-r--r--  1 root root      309 Mar 16 23:15 volume_info-1
-rw-r--r--  1 root root    14878 Mar 16 23:15 macro_inst_initial.ycp
-rw-r--r--  1 root root      677 Mar 16 23:15 disk_hda
-rw-r--r--  1 root root 68545768 Mar 16 23:15 y2log-2
-rw-r--r--  1 root root 68546102 Mar 16 23:15 y2log-1
drwx------  2 root root     4096 Mar 16 23:29 .
-rw-r--r--  1 root root   638942 Mar 16 23:35 y2log
-rw-r--r--  1 root root     6506 Mar 16 23:35 y2logmkinitrd
drwxr-xr-x 14 root root     4096 Mar 18 00:12 ..
turion:0 00:15:57 /var/log # 

Created attachment 73782 [details]
Misssing, due to bugzilla stupidity.

OK, deleted y2log-2 because y2log-1 was a superset of it,

Crazy - still too big (6 MB), and it first lets transfere it and then I get the error message. Please cure this! Either by allowing bigger uploads, or giving the error at start and not at end...

So I am not able to send the requested info due to bugzilla restrictions.

Created attachment 73802 [details]
/var/log/YaST2, part1

part 1 of /var/log/YaST2/

Created attachment 73803 [details]
/var/log/YaST2/ part 2

part2 of /var/log/YaST2/

*** Bug 159322 has been marked as a duplicate of this bug. ***

Eberhard, you can use bzip2 for a better compression next time, it might help a bit.

`cd /var/log/`
`tar -jcf YaST2.bzip2 YaST2`

It would not have helped in this case.
Bugzilla does not accept attachments > 5 MB.

There is a workaround: rearrange the free space, not a blocker.

Sorry, this is not a valid workaround in a given production environment;
especially as it worked before, i.e. including Beta 6 AFAIK.
Setting to BLOCKER again.
so short MgE

No, it did not work before. Up to beta6 we did not check the space at all.

That's not an excuse. It also worked in SLES 8 and SLES 9,
and I doubt, that the requirements allow a degradation in functionality.
Working in the Linux enterprise Environment for about 7 years now,
this is a blocker and will never be anything else.

so short MgE
-- 
Matthias G. Eckermann
Senior Linux and Open Source Architect
Novell Linux SWAT Team EMEA 

*** Bug 159660 has been marked as a duplicate of this bug. ***

Will this be fixed in Beta9?

Holgi, did your tests cover such scenario by any chance?

It won't be fixed for Beta9.

Do you still need info from eberhard?  If yes, please ask him to provide it via other means.

Proposal:

Could we, please, have a workaround, that the user can decide,
to allow installation regardless the (virtually) missing space?
"Proceed Anyway?" Yes - No

I think, it would be easy to add an corresponding query  instead of a warning in:
/usr/share/YaST2/modules/SpaceCalculation.ycp function "CheckDiskSize"
(on the "root"-disk).

Thanks - MgE

The query is allready there, but doesn't allow you to continue ;-(

A warning is good enough for a beta, but certainly not for R.C.!!
Otherwise back to b6-situation: no checking (at that point at least)
AFAIK, space checking is also done during software selection.

In the final product, you can not say "there might be a problem with diskspace, but don't be alarmed, because we can not calculate your free space currently"
People would bail out!

I fully agree. My proposal was _only_, until the real calculation-bug
is fixed; it at least would allow, to install, what you selected _now_.

I couldn't find the proposal blocker in the log, the only log I found were unresolved dependencies. Probably due to the size of the log, the error has not been preserved.

Are you able to reproduce the bug (with the latest beta)? If you are, please, grab the log when the void proposal blocking error appears, and attach them, they should be shorter.

Thanks in advance!

The red warning is still there, but it is not blocking any longer.
I did y2pmsh "upgrade" with last week's factory and then a YaST2 "system update" against today's factory.
I just was able to proceed against the red warning today.

beta9 still exhibits this bug, and it seems to be a pretty serious one.
It's not taking into account the fact that my /usr and /var (and /opt, etc...) are on different partitions than /.

This is /very/ easy to reproduce - make your / partition, say, 1G and make additional partitions /usr, /opt, and /var and select (for example) to install the KDE desktop. That is 1.9G and will not fit into / alone, but more than enough when /usr and /opt are included.

I am able to reproduce;see bug #162846 for the logs. No need to duplicate here.

Of course, I don't have access to view bug 162846, but I'll assume y'all are working on it.

*** This bug has been marked as a duplicate of 163197 ***

Reading bug #163197 I heavily doubt, that this is the same problem.
Please read carefully, to see, why. Thanks.

Feel free to describe here why it's different. Until then, this is fixed as duplicate.

(In reply to comment #16)
> Will this be fixed in Beta9?
> 

I had the same during Installation of beta9 using LVM on IBM p550
I take the workaround to increase / by 12 MB

After initial Installation I installed KDE und received also a warning
about low disk-space but thisone it could be ignored. 

seems I don't have access to bug #162846 and #1633197 so I this message here

*** This bug has been marked as a duplicate of 163197 ***

This bug is still present in RC1.

Reproduced on fresh install of RC1 from DVD (made out of CDs).
Setup: 300MB / partition plus VG with 3GB /usr and 3GB /opt plus smaller /tmp and /var. YaST complains about lack of disk space. "Continue anywas" option has no effect. There's no way to circumvent that faulty disk space check. Nasty.

*** Bug 167200 has been marked as a duplicate of this bug. ***

I fear the only solution right now is to make this just a warning on update.

The counting of disk space on separate patitions should be fixed in RC2 (see #163199).

I agree with switching the message to warning level, disk usage counting in update mode is not accurate and it could prevent from update of a system.

Fixed in yast2-packager-2.13.86