Oh yes you are right, I was sure it was detected by fsck but
apparently it's not like that.
Anyway, the corruption is exposed by the Linux ext4 fs implementation,
just mount the initrd.img image and fill the remaining free space;
the following error message will be printed by the kernel:
EXT4-fs error (device loop0): ext4_mb_complex_scan_group:1916: group
6, 402 free clusters as per group info. But got 512 blocks
According to the Linux source code it means that
ext4_grp_locked_error(sb, e4b->bd_group, 0, 0,
"%d free clusters as per "
"group info. But got %d blocks",
free, ex.fe_len);
/*
* The number of free blocks differs. This mostly
* indicate that the bitmap is corrupt.
On Mon, Dec 16, 2013 at 12:06 AM, Martin Sucha <[email protected]> wrote:
> Hi Maurizio,
>
> I tried running fsck on initrd.img produced by a build of the latest
> mainline (2043) and it seems to be OK:
>
> $ fsck.ext2 -f boot/distroot/boot/initrd.img
> e2fsck 1.42.5 (29-Jul-2012)
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> HelenOS_rdimage: 301/3584 files (1.3% non-contiguous), 6070/7168 blocks
>
> Can you please post the corrupted image you mentioned at the last
> meeting? Or steps to reproduce?
>
> Thanks.
>
> Martin
>
> _______________________________________________
> HelenOS-devel mailing list
> [email protected]
> http://lists.modry.cz/listinfo/helenos-devel
--
--------------------
Maurizio Lombardi
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
