I believe that I'm also running into this bug except in my case
mksquashfs (from squashfs-tools 1:4.0-8) is being invoked by live-helper
(now known as live-build). Occasionally, mksquashfs will hang at
seemingly 100%. I've captured the following debug information:
`-lh_build,16803
There is still a halting problem in mksquashfs 4.1, but it's MUCH rarer
than it was in 4.0. I'm guessing one hang in 300 invocations.
I've written a (horrible) way around the problem, which is to call
mksquashfs indirectly via a Python program that kills mksquashfs and re-
invokes mksquashfs,
I took Philip Lougher's advice to heart. I downloaded mksquashfs 4.1
source from Sourceforge, compiled it, and my hanging problem has not
occurred since.
I therefore urge that the squashfs-tools package in Ubuntu be upgraded
from 4.0 to 4.1. When that happens, this bug will be history.
--
You
On 02/22/2011 11:08 PM, Phillip Lougher wrote:
Where is the output of mksquashfs going?
To a pipe, and thence to a file. But I suspect that I'm flushing it
frequently, which may contribute greatly to the problem. I'll have to
look into that.
The -noappend option changing things is
Well, I'm trying a run with -info and -no-progress , but, gosh, -info
really seems to slow the mksquashfs process down to a small fraction of
its usual speed (I'm not sure why, or whether it's my fault somehow).
At this rate, it could be weeks before I finish a single run, so don't
hold your
-info makes Mksquashfs write to stdout for every file it squashes, and
so yes, -info will probably slow things down if you've got lots of small
files, and stdout is throttled in some way (i.e. mksquashfs waits on
stdout). Where is the output of mksquashfs going? If it's going to
the console
Dear Mr. Lougher,
(1) Here's something else for you to think about; it may be relevant to
the solution of the mystery. Trying to make a workaround for the
problem, I wrote a Python tool (syscall.py) that I could call from the
Transparent Archivist to call mksquashfs with a timeout and an
Answers to your questions follow:
On 02/21/2011 12:08 AM, Phillip Lougher wrote:
As far as mksquashfs is concerned, it is being invoked in the usual way
as an independent subprocess.
What is the exact command line passed to Mksquashfs? (from looking at
the Transparent Archivist tool's source
-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
As far as mksquashfs is concerned, it is being invoked in the usual way
as an independent subprocess.
What is the exact command line passed to Mksquashfs? (from looking at
the Transparent Archivist tool's source code it doesn't seem to be
passing any non-standard options).
Sometimes -- not very
10 matches
Mail list logo
