-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
PROTECTED]
Subject: Re: problem: Corrupted filesystem
I apologize for my delay in the reply
What I have do exactly is just not-use the lzma compression for now, but Im
not sure to use it due to the more high cpu needed in the decompression so,
everytime something on the system is readed
This is why i
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
[EMAIL PROTECTED]:
The real cause was NOT in aufs (or unionfs), but in squashfs, more exactly
due to the LZMA compression, more information in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456489
It seems that debian people failed to apply sqlzma patch for squashfs,
or to build their
Tomas M:
I just received several reports (from 5 different people) that they are
trying to build a Live CD, and their squashfs filesystems seem corrupted
(while extracting the squashfs image using unsquashfs results in 100% correct
data).
So it seems to me like a problem with squashfs
On Wed February 20 2008 08:13, [EMAIL PROTECTED] wrote:
Tomas M:
I just received several reports (from 5 different people) that they are
trying to build a Live CD, and their squashfs filesystems seem corrupted
(while extracting the squashfs image using unsquashfs results in 100%
[EMAIL PROTECTED] wrote:
Tomas M:
I just received several reports (from 5 different people) that they are
trying to build a Live CD, and their squashfs filesystems seem corrupted
(while extracting the squashfs image using unsquashfs results in 100%
correct data).
So it seems to me like a