Bug 156149 - nearly empty y2logs on machines with lots of memory (>6GB)
Summary: nearly empty y2logs on machines with lots of memory (>6GB)
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-08 17:08 UTC by Martin Vidner
Modified: 2006-03-10 15:02 UTC (History)
2 users (show)

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 Martin Vidner 2006-03-08 17:08:12 UTC 
In bug 152575 comment 1, the attached y2logs all have only a single line.

y2start.log says MemFree="8049064" and Maximum log size: 2668072 Kb. I assume that an overflow occurs in liby2util's y2log.cc

I think it's a blocker because we're unable to debug yast installation on such machines.

Also, working around it by specifying Y2MAXLOGSIZE on the kernel command line will not work because of the flawed logic in installation/startup/First-Stage/F08-logging. (The user should have the last word.)
Comment 1 Michal Svec 2006-03-09 09:10:33 UTC 
To the first part (y2log.cc), it's using off_t due to stat(2) which can be the culprit. However, I'd expect it should be LARGEFILE-compatible automatically as the system supports it.
Comment 2 Martin Vidner 2006-03-10 14:21:26 UTC 
ppc64 userland has 32 bit off_t. The problem is the conversion from kilobytes to bytes, an overflow occurs there.
I have put a fixed liby2util-2.13.7 to SVN.
Comment 3 Martin Vidner 2006-03-10 15:02:34 UTC 
submitted