Re: Problem with ISO9660 and files stored on multiple extents

[Carlo Caione]

On Thu, Feb 16, 2017 at 5:52 PM, Andrei Borzenkov <address@hidden> wrote:
> 16.02.2017 19:04, Vladimir 'phcoder' Serbinenko пишет:
>> On Thu, Feb 16, 2017, 16:56 Carlo Caione <address@hidden> wrote:

>> Then it's possible that your patch is correct. I don't know why the format
>> changes or what the 0 means in this field
>>
>
> Looking at current squash tools git, 0 is valid fragment number. Any
> chance we hit different file type here? Carlo, could you make your
> squashfs image available?

Here the whole non-booting ISO
https://d1anzknqnc1kmb.cloudfront.net/eos-amd64-amd64/eos3.1/sea/170214-155339/eos-eos3.1-amd64-amd64.170214-155339.sea.iso
(`endless/endless.squash` is the squash image)
`qemu-system-x86_64 -m 512 -machine q35,accel=kvm -hda $iso` drops you
into a GRUB shell (same booting with EFI). For smaller images it boots
fine.

We actually solved this problem creating the squashfs passing the
option `-no-fragments` to `mksquashfs`. So I guess that really the
squash4 module has some bug when dealing with big images with a number
of fragments !=0.

-- 
Carlo Caione  |  +39.340.80.30.096  |  Endless