-no-sparse isn't going to have any effect here, this was a workaround for some sparse file handling bugs that were fixed for Mksquashfs 3.4 (i.e. sometime before Mksquashfs 4.0 which you're using). LikewSise, the -no-lzma mess was due to a mismatch between Ubuntu's patched Mksquashfs (inherited from Debian) and Ubuntu's kernel Squashfs code which not being derived from Debian lacked their lzma patches. Again these are not relevant here because it is not a squashfs-tools/kernel code interoperability problem, and in any case that problem went away a couple of Ubuntu releases ago.
So what is the problem? From your description it sounds like a multi- threading synchronisation problem. One extremely rare synchronisation bug has come to light since Mksquashfs 4.0, plus some other bugs have come to light since Mksquashfs 4.0, which could possibly cause Mksquashfs to get sufficiently confused to hang. On the other hand this is the first Mksquashfs hang reported against Mksquashfs 4.0 in nearly two years since it's release... and on that basis the threading code seems to be very stable and almost bug free. You may of course be extremely unlucky and have a hardware/source filesystem combination that's triggered the bugs fixed in Mksquashfs 4.1, or an unknown bug. I would suggest your first step is to download squashfs-tools 4.1 from squashfs.sourceforge.net, and see if the problem still occurs. If the problem still occurs then your second step should be to raise a bug on the Squashfs bug tracker (squashfs.sourceforge.net). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/722168 Title: mksquashfs hangs -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
