[Pkg-ltsp-devel] Bug#466467: ltsp-server: ltsp-update-image does not work

[José L. Redrejo Rodríguez]

El mar, 26-02-2008 a las 10:43 -0800, vagrant at freegeek.org escribió:
> On Tue, Feb 19, 2008 at 12:03:09AM +0100, José L. Redrejo Rodríguez wrote:
> > Package: ltsp-server
> > Version: 5.0.40~bzr20071229-1
> 
> i'm guessing this hasn't changed with ltsp-server 5.0.40~bzr20080214-1 ?
>  

Right, it's the same

> > With the new squashfs-tools that migrated to lenny on 2008-02-11, 
> 
> i believe you're referring to squashfs-tools version 1:3.3-3 ?
> 

Right

> which version(s) do you know do work?
> 

All versions up to 1:3.2r2-9. I've tried with all the versions uploaded
later beginning with 3.2r2-9exp1 and none of them work.

> > the script ltsp-update-image does not work anymore. 
> 
> well, i kept the default to NFS for a reason. :)
> 

Now you have a good reason ;-)

> > It seems the default behaviour of mksquashfs has changed in Debian and
> > the img file is created but can not be uncompressed from the pxe-initrd
> > image.
> 
> might this be related to:
> 
>  #456489: squashfs-tools: data corruption caused by lzma patches 
>  #455589: squashfs-tools: mksquashfs hangs with zlib and lzma
> 
>  455589 claims to be fixed in 1:3.3-3, which seems to be when you
>  started encountering the problem.
>  

Not, because in my tests I even compiled 3.3-1 to 3.3-3 removing the
lzma patch and it failed the same. Removing the lzma patch from
3.2r2-9exp1 made it work, but not with 3.3. I've also compiled the clean
upstream 3.3 version without Debian patches and it also fails. There is
something that changed from 3.2 to 3.3 that broke it.


> > I've tried to use the -nolzma option in the mksquashfs execution at
> > ltsp-update-image but it does not work either.
> 
> seems likely a bug in mksquashfs... if not one of the already reported
> bugs, then some new bug. i almost thing this bug should be reassigned to
> squashfs-tools (or a new bug filed and mark it as blocking this bug).

It's pretty reasonable, but it might also be some config that should be
changed in ltsp-update-image to make it work. Obviously mksquashfs and
unsquashfs work perfectly on the ltsp-server, so I don't know how to
report this bug in the squashfs-tool package as it seems only a problem
when using squashfs-tools with ltsp.

>  
> > I can make more tests if some ideas, options or workarounds are
> > possible.
> 
> you probably have much more experience with this mode of operation than
> i do...
> 

Maybe with the operation I have more experience but I do not have a good
knowledge of how the image is uncompressed and mounted from the initrd
when the ltsp terminal starts. The fix could be something as stupid as
setting some parameter for squashfs.ko.

Regards.
José L.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente
Url : http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/attachments/20080226/0809510d/attachment.pgp