Red Hat Bugzilla – Bug 181046
upgrade hangs mmapping huge lastlog
Last modified: 2007-11-30 17:11:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:184.108.40.206) Gecko/20060208 Debian/1.5.dfsg+220.127.116.11-1 Firefox/18.104.22.168
Description of problem:
I installed fc3 minimal, then tried to do up2date -u -- I tracked it down to upgrading shadow-utils. I downloaded shadow-utils-4.0.3-56.x86_64.rpm and tried to install by hand, and it hung, and top showed that it is using over a terabyte of virtual memory. I straced it, and found it was mmapping /var/log/lastlog, which, possibly because something "logged in" as nfsnobody, was (sort of) a >1 terabyte file (yeah, I know it's really a sparse file, as described in https://www.redhat.com/archives/fedora-list/2005-March/msg00076.html but apparently mmap doesn't fully understand that, or at least does something stupid. As a workaround, I rm -f'ed /var/log/lastlog and installed the rpm, but it's clearly broken, and took me many hours to figure out.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I don't see an easy way of getting the /var/log/lastlog file to go into "huge" mode again without scratch installing the whole system, which I really don't have time to do right now-- sorry.
oops, I didn't fully describe the hang (and didn't proofread too well, sorry),
and I'm guessing (but haven't tested) that the way to duplicate is to:
-- scratch install fc3 from iso images, choose minimal install
-- download shadow-utils-4.0.3-56.x86_64.rpm
-- rpm -v -i shadow-utils-4.0.3-56.x86_64.rpm
-- look! it hangs and top thinks it's using a terabyte of VM!
this assumes that whatever made a lastlog entry for nfsnobody during my install
is repeatable. But from googling, it appears that the huge lastlog file is not
too rare an issue for 64bit fedora/rh systems.
This bug is fixed in FC-4.
Huge lastlog file was created during nfs-utils instalation on 64bit platforms.
>I don't see an easy way of getting the /var/log/lastlog file to go into "huge"
>mode again without scratch installing the whole system, which I really don't
have >time to do right now-- sorry.
There's no need to do this.