#1 empty inode entry in 2.2r2 causes filesystem failure

closed
nobody
None
5
2008-02-03
2006-06-14
A_v
No

Hi,

I am trying to use the squashfs version 2.2r2 to
generate a compressed filesystem image, using the
following:

/PATH_TO_TOOLS/squashfs-tools/mksquashfs
/tmp/DIR_TO_SQUASH/* output.img -noappend -nopad -info
-le -all-root

The problem is that sometimes I see that sometimes that
there is an empty directory inode that is created:

"mksquashfs: directory inode 0x912"

Whenever this happens the filesystem image that is
created can't be read.

I was wondering if anyone else had seen this problem
and if they have, is there a workaround for it?

Thanks,
AV.

Discussion

    • status: open --> closed
     
  • Logged In: YES
    user_id=621656
    Originator: NO

    This issue should not occur in Mksquashfs 2.2-r2. I have tried to reproduce this bug using Mksquashfs 2.2-r2 and I cannot get this bug to occur. This is also an old release and is not supported any more. Please retest with the latest 3.3 release and resubmit if it still occurs. Closing this bug because it has been here for a number of years, and I've never been able to reproduce the bug.