| Summary: | sys-fs/squashfs-tools: mksquashfs has memleaks | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matthias Liertzer <m_liertzer> |
| Component: | Current packages | Assignee: | Gentoo LiveCD Package Maintainers <livecd> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | critical | CC: | embedded |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Matthias Liertzer
2004-09-29 16:38:12 UTC
I forgot to mention that I've already tried version 2.0 and 2.0_p2 of squashfs, both appear to have the same problem. I just compiled squashfs using gcc-3.3.4-r1 ( eval 'gcc-config -E 1'; emerge squashfs-tools ) and the problem is still there. The problem only seems to occur, when dealing with rather big files, atm, the final squashfs-build should have a size of about 300Mib Reassigning to the maintainer adding embedded@ cuz we care about squashfs solar@simple ~ $ metadata.py sys-fs/squashfs-tools Package: sys-fs/squashfs-tools Herd: livecd Maintainer: livecd I'm just curious, but how much swap/RAM do you have? 256MB memory + 256 MB swap Sounds invalid to me. Somebody with >=1G Ram should test. I honestly think there's a good possibility that you're memory-starving catalyst. I build LiveCDs almost daily and I can tell you that I eat through a *lot* more memory than that pretty easily with my system doing nothing else. Are you sure you just aren't running out of memory? Works fine here on 512MB RAM + 1.5GB swap (and I swap on this machine when building minimal ISOs), on my laptop with 1GB of RAM (no swapping), and on my main machine with 2GB. ok, I mistyped my swap-space in the last comment, I have 512 MB of swap space, so about 768MB virtual memory. At the moment I solved my particular problem by simply putting this ~300mb bzipped tar-file into the isolinux-directory, instead of the squahfs-dir structure. Now mksquashfs works without a problem. So the problem hast to be this large file. the memory usage of mksquashfs with the 300mb file in the directory structure looks roughly like that: Most of the time it has a memory usage according to 'top' of about 3 to 4%, seems to be perfectly normal, then after about 2 minutes, it suddenly starts to allocate memory very quickly. five seconds later I can hear heavy disk access => the kernel is starting to swap and I can't interact with either mksquashfs nor with top after a few seconds.( Ctrl + C and q don't work ) Well, sounds like a bug to me... And I don't really think that more than 750 mb of virtual memory is needed for creating a ~320 mb squashfs.... Are you running mksquashfs while in X? Have any high-load daemons running? Gnome? KDE? I've been working on the 2004.3 LiveCD and I'm not quite sure that you aren't running out of RAM/swap. I have 2GB in my machine and making the squashfs image seems to sake quite a bit of power. I'll perform another run of just making the squashfs image and post here. I just compressed a 1G system down to 258M on my laptop just now with only 512M and no swap. vote WORKSFORSOME Sounds good to me... considering we've been building releases like crazy wit it and have seen no such problems. I'll give it another try on the weekend, I'll report the results then |
