Fixed
Created: Dec 22, 2016
Updated: Dec 3, 2018
Resolved Date: Dec 26, 2016
Found In Version: 6.0.0.31
Fix Version: 6.0.0.32
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Host Tools, Userspace
genext2fs command prints out the below message continuously, for hours, and never ends
The same command works in wrlinux-3.
--- genext2fs -b 1060000 stock-pl-ramdisk -v -d export/dist-mod/
...
.......................................................
inode bitmap allocation:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
***************************.....
inode 2 (root, 20 links): drwxr-xr-x, size: 1024 bytes (1 block)
blocks in inode 2: 13
1 blocks (1024 bytes)
directory for inode 2:
entry '.' (inode 2): rec_len: 12 (name_len: 1)
entry '..' (inode 2): rec_len: 12 (name_len: 2)
entry 'lost+found' (inode 33): rec_len: 20 (name_len: 10)
entry 'tmp' (inode 65): rec_len: 12 (name_len: 3)
entry 'lib' (inode 97): rec_len: 12 (name_len: 3)
entry 'root' (inode 3586): rec_len: 12 (name_len: 4)
entry 'var' (inode 3716): rec_len: 12 (name_len: 3)
entry 'usr' (inode 3336): rec_len: 12 (name_len: 3)
entry 'sys' (inode 2615): rec_len: 12 (name_len: 3)
entry 'media' (inode 2231): rec_len: 16 (name_len: 5)
entry 'bin' (inode 1943): rec_len: 12 (name_len: 3)
entry 'lib64' (inode 778): rec_len: 16 (name_len: 5)
entry 'boot' (inode 1240): rec_len: 12 (name_len: 4)
entry 'home' (inode 760): rec_len: 12 (name_len: 4)
entry 'run' (inode 2840): rec_len: 12 (name_len: 3)
entry 'etc' (inode 120): rec_len: 12 (name_len: 3)
entry 'proc' (inode 3994): rec_len: 12 (name_len: 4)
entry 'sbin' (inode 2234): rec_len: 12 (name_len: 4)
entry 'dev' (inode 955): rec_len: 12 (name_len: 3)
entry 'mnt' (inode 1211): rec_len: 780 (name_len: 3)
Done with inode 2
Group No: 35
block bitmap: block 277447,inode bitmap: block 277448, inode table: block 277449
block bitmap allocation:
----+----1----+----2----+---
...
---
1. create platform project and build it
configure --enable-board=intel-x86-64 --enable-kernel=standard --enable-rootfs=glibc_small --enable-reconfig
2. extract the root FS tarball in dist-mod (newly created directory)
$ ls -l export/intel-x86-64-glibc-small-standard-dist.tar.bz2
lrwxrwxrwx 1 wrsupport wrsupport 94 Jun 28 18:24 export/intel-x86-64-glibc-small-standard-dist.tar.bz2 -> ../bitbake_build/tmp/deploy/images/intel-x86-64/wrlinux-image-glibc-small-intel-x86-64.tar.bz2
$ ls -l bitbake_build/tmp/deploy/images/intel-x86-64/wrlinux-image-glibc-small-intel-x86-64.tar.bz2
lrwxrwxrwx 1 wrsupport wrsupport 68 Jun 28 18:24 bitbake_build/tmp/deploy/images/intel-x86-64/wrlinux-image-glibc-small-intel-x86-64.tar.bz2 -> wrlinux-image-glibc-small-intel-x86-64-20160628220813.rootfs.tar.bz2
$ ls -l bitbake_build/tmp/deploy/images/intel-x86-64/wrlinux-image-glibc-small-intel-x86-64-20160628220813.rootfs.tar.bz2
-rw-r--r-- 1 wrsupport wrsupport 38435814 Jun 28 18:24 bitbake_build/tmp/deploy/images/intel-x86-64/wrlinux-image-glibc-small-intel-x86-64-20160628220813.rootfs.tar.bz2
mkdir dist-mod
cd dist-mod
sudo tar xvjf ../intel-x86-64-glibc-small-standard-dist.tar.bz2
cd ..
sudo chmod -R 777 dist-mod
3. generate the 2GB ext2 filesystem (in the real usecase, customer adds its application and adds/removes other files to dist-mod
genext2fs -b 2060000 stock-pl-ramdisk -v -d export/dist-mod/
--> last command never ends and displays the log mentioned in the description.