unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Todd Stellanova]

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

Hello,

I'm following these directions for building with yocto for the wandboard:
http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard

I'm building a bb recipe based on core-image-minimal-dev, to which I've
added:
IMAGE_FEATURES += "package-management"

In my conf/local.conf I originally had:
PACKAGE_CLASSES ?= "package_rpm"

This built fine and I was able to boot with the resulting sdcard image fine
on the wandboard. However, I'd like to use opkg on the wandboard for
package management, so I modified local.conf to:
PACKAGE_CLASSES ?= "package_ipk"

and bitbaked my image again.  The resulting sdcard image doesn't boot on
the wandboard, and if I look at the sdcard image I can see that, for
example, /etc is completely missing from the rootfs.

Do I need to do anything else to switch the build to properly using ipks
with opkg?

Thanks for any help!

[-- Attachment #2: Type: text/html, Size: 2290 bytes --]

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Todd Stellanova]

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

It appears that copying the files to the ext3 / sdcard image is failing in
*populate-extfs.sh*
I see a series of these errors:

*copy_file: Could not allocate block in ext2 filesystem*

Any idea what might cause this?  I've verified that the initial .tar
archive and the bz2 contain the right files.



On Sat, Nov 23, 2013 at 10:22 AM, Todd Stellanova <tstellanova@gmail.com>wrote:

> Hello,
>
> I'm following these directions for building with yocto for the wandboard:
> http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard
>
> I'm building a bb recipe based on core-image-minimal-dev, to which I've
> added:
> IMAGE_FEATURES += "package-management"
>
> In my conf/local.conf I originally had:
> PACKAGE_CLASSES ?= "package_rpm"
>
> This built fine and I was able to boot with the resulting sdcard image
> fine on the wandboard. However, I'd like to use opkg on the wandboard for
> package management, so I modified local.conf to:
> PACKAGE_CLASSES ?= "package_ipk"
>
> and bitbaked my image again.  The resulting sdcard image doesn't boot on
> the wandboard, and if I look at the sdcard image I can see that, for
> example, /etc is completely missing from the rootfs.
>
> Do I need to do anything else to switch the build to properly using ipks
> with opkg?
>
> Thanks for any help!
>

[-- Attachment #2: Type: text/html, Size: 3359 bytes --]

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Nicolas Dechesne]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova <tstellanova@gmail.com>wrote:

> It appears that copying the files to the ext3 / sdcard image is failing in
> *populate-extfs.sh*
> I see a series of these errors:
>
> *copy_file: Could not allocate block in ext2 filesystem*
>
> Any idea what might cause this?  I've verified that the initial .tar
> archive and the bz2 contain the right files.
>

can you try to create a new <build> folder (do not remove the current one
for now) and reuse the downloads and sstate folder? i am wondering if there
is a bug when trying to change PACKAGE_CLASSES in an existing <build>
folder.

[-- Attachment #2: Type: text/html, Size: 1380 bytes --]

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Paul Eggleton]

Hi Nicolas / Todd,

On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
> On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
> <tstellanova@gmail.com>wrote:
> > It appears that copying the files to the ext3 / sdcard image is failing in
> > *populate-extfs.sh*
> > I see a series of these errors:
> > 
> > *copy_file: Could not allocate block in ext2 filesystem*
> > 
> > Any idea what might cause this?  I've verified that the initial .tar
> > archive and the bz2 contain the right files.
> 
> can you try to create a new <build> folder (do not remove the current one
> for now) and reuse the downloads and sstate folder? i am wondering if there
> is a bug when trying to change PACKAGE_CLASSES in an existing <build>
> folder.

I do this not infrequently and never hit a problem like this, so I doubt this 
is the case.

Either there is a problem in how the filesystem is being set up (block sizes, 
etc.) or there is some kind of corruption occurring.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Todd Stellanova]

Thanks for the ideas. I'll try creating a new build folder. If that still shows the problem, I'm thinking this has something to do with the fact that I'm running the build inside a vm (inside an Ubuntu vm running on a Mac). It looks like the build is using debugfs...maybe it's running out of ram at some point and not obtaining more in the vm properly?

> On Nov 25, 2013, at 5:21 AM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> 
> Hi Nicolas / Todd,
> 
>> On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
>> On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
>> <tstellanova@gmail.com>wrote:
>>> It appears that copying the files to the ext3 / sdcard image is failing in
>>> *populate-extfs.sh*
>>> I see a series of these errors:
>>> 
>>> *copy_file: Could not allocate block in ext2 filesystem*
>>> 
>>> Any idea what might cause this?  I've verified that the initial .tar
>>> archive and the bz2 contain the right files.
>> 
>> can you try to create a new <build> folder (do not remove the current one
>> for now) and reuse the downloads and sstate folder? i am wondering if there
>> is a bug when trying to change PACKAGE_CLASSES in an existing <build>
>> folder.
> 
> I do this not infrequently and never hit a problem like this, so I doubt this 
> is the case.
> 
> Either there is a problem in how the filesystem is being set up (block sizes, 
> etc.) or there is some kind of corruption occurring.
> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Todd Stellanova]

[-- Attachment #1: Type: text/plain, Size: 3183 bytes --]

Tried creating a fresh build folder and giving the vm more ram but the
results are basically the same:

Allocated inode: 15264
copy_file: Could not allocate block in ext2 filesystem
debugfs: sif "libgio-2.0.so.0.3800.1" mode 0x81ed

It appears that using package_rpm successfully allocates something like
15968 inodes. When calculating the ROOTFS_SIZE it looks like package_rpm
and package_ipk are using very different values:

package_rpm:

++ du -ks
/fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new/1.0-r0/rootfs
++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size :
8192) + 0 + *51200*); if (base_size != int(base_size)) base_size =
int(base_size + 1); base_size = base_size + 4096 - 1; base_size -=
base_size % 4096; print base_size }'

+ ROOTFS_SIZE=*458752*

package_ipk:

++ du -ks
/fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new/1.0-r0/rootfs
++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size :
8192) + 0); if (base_size != int(base_size)) base_size = int(base_size +
1); base_size = base_size + 4096 - 1; base_size -= base_size % 4096; print
base_size }'

+ ROOTFS_SIZE=*376832*

I'm just guessing here, but it seems like package_ipk is underestimating
ROOTFS_SIZE and subsequently populate-extfs.sh fails trying to add files to
the ext fs.  Any ideas what might cause this?

Thanks for any help!






On Mon, Nov 25, 2013 at 7:03 AM, Todd Stellanova <tstellanova@gmail.com>wrote:

> Thanks for the ideas. I'll try creating a new build folder. If that still
> shows the problem, I'm thinking this has something to do with the fact that
> I'm running the build inside a vm (inside an Ubuntu vm running on a Mac).
> It looks like the build is using debugfs...maybe it's running out of ram at
> some point and not obtaining more in the vm properly?
>
> > On Nov 25, 2013, at 5:21 AM, Paul Eggleton <
> paul.eggleton@linux.intel.com> wrote:
> >
> > Hi Nicolas / Todd,
> >
> >> On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
> >> On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
> >> <tstellanova@gmail.com>wrote:
> >>> It appears that copying the files to the ext3 / sdcard image is
> failing in
> >>> *populate-extfs.sh*
> >>> I see a series of these errors:
> >>>
> >>> *copy_file: Could not allocate block in ext2 filesystem*
> >>>
> >>> Any idea what might cause this?  I've verified that the initial .tar
> >>> archive and the bz2 contain the right files.
> >>
> >> can you try to create a new <build> folder (do not remove the current
> one
> >> for now) and reuse the downloads and sstate folder? i am wondering if
> there
> >> is a bug when trying to change PACKAGE_CLASSES in an existing <build>
> >> folder.
> >
> > I do this not infrequently and never hit a problem like this, so I doubt
> this
> > is the case.
> >
> > Either there is a problem in how the filesystem is being set up (block
> sizes,
> > etc.) or there is some kind of corruption occurring.
> >
> > Cheers,
> > Paul
> >
> > --
> >
> > Paul Eggleton
> > Intel Open Source Technology Centre
>

[-- Attachment #2: Type: text/html, Size: 4277 bytes --]

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Paul Eggleton]

Robert, since I think you implemented this, any idea what might be going wrong 
here?

Cheers,
Paul

On Tuesday 26 November 2013 17:27:30 Todd Stellanova wrote:
> Tried creating a fresh build folder and giving the vm more ram but the
> results are basically the same:
> 
> Allocated inode: 15264
> copy_file: Could not allocate block in ext2 filesystem
> debugfs: sif "libgio-2.0.so.0.3800.1" mode 0x81ed
> 
> It appears that using package_rpm successfully allocates something like
> 15968 inodes. When calculating the ROOTFS_SIZE it looks like package_rpm
> and package_ipk are using very different values:
> 
> package_rpm:
> 
> ++ du -ks
> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new
> /1.0-r0/rootfs ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192
> ? base_size : 8192) + 0 + *51200*); if (base_size != int(base_size))
> base_size = int(base_size + 1); base_size = base_size + 4096 - 1; base_size
> -= base_size % 4096; print base_size }'
> 
> + ROOTFS_SIZE=*458752*
> 
> package_ipk:
> 
> ++ du -ks
> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new
> /1.0-r0/rootfs ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192
> ? base_size : 8192) + 0); if (base_size != int(base_size)) base_size =
> int(base_size + 1); base_size = base_size + 4096 - 1; base_size -=
> base_size % 4096; print base_size }'
> 
> + ROOTFS_SIZE=*376832*
> 
> I'm just guessing here, but it seems like package_ipk is underestimating
> ROOTFS_SIZE and subsequently populate-extfs.sh fails trying to add files to
> the ext fs.  Any ideas what might cause this?
> 
> Thanks for any help!
> 
> On Mon, Nov 25, 2013 at 7:03 AM, Todd Stellanova 
<tstellanova@gmail.com>wrote:
> > Thanks for the ideas. I'll try creating a new build folder. If that still
> > shows the problem, I'm thinking this has something to do with the fact
> > that
> > I'm running the build inside a vm (inside an Ubuntu vm running on a Mac).
> > It looks like the build is using debugfs...maybe it's running out of ram
> > at
> > some point and not obtaining more in the vm properly?
> > 
> > On Nov 25, 2013, at 5:21 AM, Paul Eggleton <
> > paul.eggleton@linux.intel.com> wrote:
> > > On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
> > > > On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
> > > > <tstellanova@gmail.com>wrote:
> > > > > It appears that copying the files to the ext3 / sdcard image is
> > > > > failing in *populate-extfs.sh*I see a series of these errors:
> > > > > 
> > > > > *copy_file: Could not allocate block in ext2 filesystem*
> > > > > 
> > > > > Any idea what might cause this?  I've verified that the initial .tar
> > > > > archive and the bz2 contain the right files.
> > > > 
> > > > can you try to create a new <build> folder (do not remove the current
> > > > onefor now) and reuse the downloads and sstate folder? i am wondering
> > > > if there is a bug when trying to change PACKAGE_CLASSES in an existing
> > > > <build> folder.
> > > 
> > > I do this not infrequently and never hit a problem like this, so I doubt
> > > this is the case.
> > > 
> > > Either there is a problem in how the filesystem is being set up (block
> > > sizes, etc.) or there is some kind of corruption occurring.
> > > 
-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Robert Yang]

Hi Paul,

Thanks, seems not enough space when ipk ? I will try a ipk build today.

// Robert

On 11/27/2013 06:57 PM, Paul Eggleton wrote:
> Robert, since I think you implemented this, any idea what might be going wrong
> here?
>
> Cheers,
> Paul
>
> On Tuesday 26 November 2013 17:27:30 Todd Stellanova wrote:
>> Tried creating a fresh build folder and giving the vm more ram but the
>> results are basically the same:
>>
>> Allocated inode: 15264
>> copy_file: Could not allocate block in ext2 filesystem
>> debugfs: sif "libgio-2.0.so.0.3800.1" mode 0x81ed
>>
>> It appears that using package_rpm successfully allocates something like
>> 15968 inodes. When calculating the ROOTFS_SIZE it looks like package_rpm
>> and package_ipk are using very different values:
>>
>> package_rpm:
>>
>> ++ du -ks
>> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new
>> /1.0-r0/rootfs ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192
>> ? base_size : 8192) + 0 + *51200*); if (base_size != int(base_size))
>> base_size = int(base_size + 1); base_size = base_size + 4096 - 1; base_size
>> -= base_size % 4096; print base_size }'
>>
>> + ROOTFS_SIZE=*458752*
>>
>> package_ipk:
>>
>> ++ du -ks
>> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new
>> /1.0-r0/rootfs ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192
>> ? base_size : 8192) + 0); if (base_size != int(base_size)) base_size =
>> int(base_size + 1); base_size = base_size + 4096 - 1; base_size -=
>> base_size % 4096; print base_size }'
>>
>> + ROOTFS_SIZE=*376832*
>>
>> I'm just guessing here, but it seems like package_ipk is underestimating
>> ROOTFS_SIZE and subsequently populate-extfs.sh fails trying to add files to
>> the ext fs.  Any ideas what might cause this?
>>
>> Thanks for any help!
>>
>> On Mon, Nov 25, 2013 at 7:03 AM, Todd Stellanova
> <tstellanova@gmail.com>wrote:
>>> Thanks for the ideas. I'll try creating a new build folder. If that still
>>> shows the problem, I'm thinking this has something to do with the fact
>>> that
>>> I'm running the build inside a vm (inside an Ubuntu vm running on a Mac).
>>> It looks like the build is using debugfs...maybe it's running out of ram
>>> at
>>> some point and not obtaining more in the vm properly?
>>>
>>> On Nov 25, 2013, at 5:21 AM, Paul Eggleton <
>>> paul.eggleton@linux.intel.com> wrote:
>>>> On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
>>>>> On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
>>>>> <tstellanova@gmail.com>wrote:
>>>>>> It appears that copying the files to the ext3 / sdcard image is
>>>>>> failing in *populate-extfs.sh*I see a series of these errors:
>>>>>>
>>>>>> *copy_file: Could not allocate block in ext2 filesystem*
>>>>>>
>>>>>> Any idea what might cause this?  I've verified that the initial .tar
>>>>>> archive and the bz2 contain the right files.
>>>>>
>>>>> can you try to create a new <build> folder (do not remove the current
>>>>> onefor now) and reuse the downloads and sstate folder? i am wondering
>>>>> if there is a bug when trying to change PACKAGE_CLASSES in an existing
>>>>> <build> folder.
>>>>
>>>> I do this not infrequently and never hit a problem like this, so I doubt
>>>> this is the case.
>>>>
>>>> Either there is a problem in how the filesystem is being set up (block
>>>> sizes, etc.) or there is some kind of corruption occurring.
>>>>

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Robert Yang]

Hi Todd,

I can't reproduce the problem, the rpm has more space than ipk is because
of the IMAGE_ROOTFS_EXTRA_SPACE, which is 50M * 1.3 by default.

Would you please try the following commands:

1) $ ls -stlh 
tmp/deploy/images/wandboard-dual/core-image-minimal-dev-wandboard-dual-*.ext3

2) $ fsck.ext4 -fn /path/to/image.ext3

And can you show the bb file if possible ?

// Robert

On 11/27/2013 09:27 AM, Todd Stellanova wrote:
> Tried creating a fresh build folder and giving the vm more ram but the
> results are basically the same:
>
> Allocated inode: 15264
> copy_file: Could not allocate block in ext2 filesystem
> debugfs: sif "libgio-2.0.so.0.3800.1" mode 0x81ed
>
> It appears that using package_rpm successfully allocates something like
> 15968 inodes. When calculating the ROOTFS_SIZE it looks like package_rpm
> and package_ipk are using very different values:
>
> package_rpm:
>
> ++ du -ks
> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new/1.0-r0/rootfs
> ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size :
> 8192) + 0 + *51200*); if (base_size != int(base_size)) base_size =
> int(base_size + 1); base_size = base_size + 4096 - 1; base_size -=
> base_size % 4096; print base_size }'
>
> + ROOTFS_SIZE=*458752*
>
> package_ipk:
>
> ++ du -ks
> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-linux-gnueabi/todd-new/1.0-r0/rootfs
> ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size :
> 8192) + 0); if (base_size != int(base_size)) base_size = int(base_size +
> 1); base_size = base_size + 4096 - 1; base_size -= base_size % 4096; print
> base_size }'
>
> + ROOTFS_SIZE=*376832*
>
> I'm just guessing here, but it seems like package_ipk is underestimating
> ROOTFS_SIZE and subsequently populate-extfs.sh fails trying to add files to
> the ext fs.  Any ideas what might cause this?
>
> Thanks for any help!
>
>
>
>
>
>
> On Mon, Nov 25, 2013 at 7:03 AM, Todd Stellanova <tstellanova@gmail.com>wrote:
>
>> Thanks for the ideas. I'll try creating a new build folder. If that still
>> shows the problem, I'm thinking this has something to do with the fact that
>> I'm running the build inside a vm (inside an Ubuntu vm running on a Mac).
>> It looks like the build is using debugfs...maybe it's running out of ram at
>> some point and not obtaining more in the vm properly?
>>
>>> On Nov 25, 2013, at 5:21 AM, Paul Eggleton <
>> paul.eggleton@linux.intel.com> wrote:
>>>
>>> Hi Nicolas / Todd,
>>>
>>>> On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
>>>> On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
>>>> <tstellanova@gmail.com>wrote:
>>>>> It appears that copying the files to the ext3 / sdcard image is
>> failing in
>>>>> *populate-extfs.sh*
>>>>> I see a series of these errors:
>>>>>
>>>>> *copy_file: Could not allocate block in ext2 filesystem*
>>>>>
>>>>> Any idea what might cause this?  I've verified that the initial .tar
>>>>> archive and the bz2 contain the right files.
>>>>
>>>> can you try to create a new <build> folder (do not remove the current
>> one
>>>> for now) and reuse the downloads and sstate folder? i am wondering if
>> there
>>>> is a bug when trying to change PACKAGE_CLASSES in an existing <build>
>>>> folder.
>>>
>>> I do this not infrequently and never hit a problem like this, so I doubt
>> this
>>> is the case.
>>>
>>> Either there is a problem in how the filesystem is being set up (block
>> sizes,
>>> etc.) or there is some kind of corruption occurring.
>>>
>>> Cheers,
>>> Paul
>>>
>>> --
>>>
>>> Paul Eggleton
>>> Intel Open Source Technology Centre
>>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Todd Stellanova]

[-- Attachment #1.1: Type: text/plain, Size: 5539 bytes --]

Thanks for taking a look at this Robert!
Below is the ls output: fsck output and bb are attached.

I should note that if I manually copy the bz2 output of bitbake to an
sdcard, like:
sudo tar xjvf
tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual.tar.bz2 -C
/media/rootfs
the image boots fine and contains all the packages I expect.

todd@ubuntu:~/proj/wandboard/fsl-community-bsp/build$ ls -stlh
tmp/deploy/images/wandboard-dual/*.ext3
572M -rw-r--r-- 1 todd todd 572M Nov 27 17:05
tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131128005017.rootfs.ext3
   0 lrwxrwxrwx 1 todd todd   50 Nov 27 17:05
tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual.ext3 ->
todd-new-wandboard-dual-20131128005017.rootfs.ext3
435M -rw-r--r-- 1 todd todd 436M Nov 26 16:17
tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131127001137.rootfs.ext3
435M -rw-r--r-- 1 todd todd 436M Nov 26 15:55
tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131126234958.rootfs.ext3
435M -rw-r--r-- 1 todd todd 436M Nov 26 15:36
tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131126232014.rootfs.ext3
435M -rw-r--r-- 1 todd todd 436M Nov 26 14:03
tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131126161048.rootfs.ext3




On Thu, Nov 28, 2013 at 4:48 AM, Robert Yang <liezhi.yang@windriver.com>wrote:

>
> Hi Todd,
>
> I can't reproduce the problem, the rpm has more space than ipk is because
> of the IMAGE_ROOTFS_EXTRA_SPACE, which is 50M * 1.3 by default.
>
> Would you please try the following commands:
>
> 1) $ ls -stlh tmp/deploy/images/wandboard-dual/core-image-minimal-dev-
> wandboard-dual-*.ext3
>
> 2) $ fsck.ext4 -fn /path/to/image.ext3
>
> And can you show the bb file if possible ?
>
> // Robert
>
>
> On 11/27/2013 09:27 AM, Todd Stellanova wrote:
>
>> Tried creating a fresh build folder and giving the vm more ram but the
>> results are basically the same:
>>
>> Allocated inode: 15264
>> copy_file: Could not allocate block in ext2 filesystem
>> debugfs: sif "libgio-2.0.so.0.3800.1" mode 0x81ed
>>
>> It appears that using package_rpm successfully allocates something like
>> 15968 inodes. When calculating the ROOTFS_SIZE it looks like package_rpm
>> and package_ipk are using very different values:
>>
>> package_rpm:
>>
>> ++ du -ks
>> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-
>> linux-gnueabi/todd-new/1.0-r0/rootfs
>> ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size
>> :
>> 8192) + 0 + *51200*); if (base_size != int(base_size)) base_size =
>>
>> int(base_size + 1); base_size = base_size + 4096 - 1; base_size -=
>> base_size % 4096; print base_size }'
>>
>> + ROOTFS_SIZE=*458752*
>>
>>
>> package_ipk:
>>
>> ++ du -ks
>> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-
>> linux-gnueabi/todd-new/1.0-r0/rootfs
>> ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size
>> :
>> 8192) + 0); if (base_size != int(base_size)) base_size = int(base_size +
>> 1); base_size = base_size + 4096 - 1; base_size -= base_size % 4096; print
>> base_size }'
>>
>> + ROOTFS_SIZE=*376832*
>>
>>
>> I'm just guessing here, but it seems like package_ipk is underestimating
>> ROOTFS_SIZE and subsequently populate-extfs.sh fails trying to add files
>> to
>> the ext fs.  Any ideas what might cause this?
>>
>> Thanks for any help!
>>
>>
>>
>>
>>
>>
>> On Mon, Nov 25, 2013 at 7:03 AM, Todd Stellanova <tstellanova@gmail.com
>> >wrote:
>>
>>  Thanks for the ideas. I'll try creating a new build folder. If that still
>>> shows the problem, I'm thinking this has something to do with the fact
>>> that
>>> I'm running the build inside a vm (inside an Ubuntu vm running on a Mac).
>>> It looks like the build is using debugfs...maybe it's running out of ram
>>> at
>>> some point and not obtaining more in the vm properly?
>>>
>>>  On Nov 25, 2013, at 5:21 AM, Paul Eggleton <
>>>>
>>> paul.eggleton@linux.intel.com> wrote:
>>>
>>>>
>>>> Hi Nicolas / Todd,
>>>>
>>>>  On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
>>>>> On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
>>>>> <tstellanova@gmail.com>wrote:
>>>>>
>>>>>> It appears that copying the files to the ext3 / sdcard image is
>>>>>>
>>>>> failing in
>>>
>>>> *populate-extfs.sh*
>>>>>> I see a series of these errors:
>>>>>>
>>>>>> *copy_file: Could not allocate block in ext2 filesystem*
>>>>>>
>>>>>> Any idea what might cause this?  I've verified that the initial .tar
>>>>>> archive and the bz2 contain the right files.
>>>>>>
>>>>>
>>>>> can you try to create a new <build> folder (do not remove the current
>>>>>
>>>> one
>>>
>>>> for now) and reuse the downloads and sstate folder? i am wondering if
>>>>>
>>>> there
>>>
>>>> is a bug when trying to change PACKAGE_CLASSES in an existing <build>
>>>>> folder.
>>>>>
>>>>
>>>> I do this not infrequently and never hit a problem like this, so I doubt
>>>>
>>> this
>>>
>>>> is the case.
>>>>
>>>> Either there is a problem in how the filesystem is being set up (block
>>>>
>>> sizes,
>>>
>>>> etc.) or there is some kind of corruption occurring.
>>>>
>>>> Cheers,
>>>> Paul
>>>>
>>>> --
>>>>
>>>> Paul Eggleton
>>>> Intel Open Source Technology Centre
>>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>

[-- Attachment #1.2: Type: text/html, Size: 8292 bytes --]

[-- Attachment #2: fsck_output.txt --]
[-- Type: text/plain, Size: 50001 bytes --]

Pass 1: Checking inodes, blocks, and sizes
Inode 21255 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21255.  IGNORED.
Illegal block #1 (1937072687) in inode 21255.  IGNORED.
Illegal block #2 (2020565625) in inode 21255.  IGNORED.
Illegal block #3 (1936682542) in inode 21255.  IGNORED.
Illegal block #4 (6580597) in inode 21255.  IGNORED.
Inode 21256 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21256.  IGNORED.
Illegal block #1 (1937072687) in inode 21256.  IGNORED.
Illegal block #2 (2020565625) in inode 21256.  IGNORED.
Illegal block #3 (1936682542) in inode 21256.  IGNORED.
Illegal block #4 (6580597) in inode 21256.  IGNORED.
Inode 21257 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21257.  IGNORED.
Illegal block #1 (1919905071) in inode 21257.  IGNORED.
Illegal block #2 (1953836645) in inode 21257.  IGNORED.
Illegal block #3 (1814916201) in inode 21257.  IGNORED.
Illegal block #4 (2020961897) in inode 21257.  IGNORED.
Inode 21260 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21260.  IGNORED.
Illegal block #1 (1937072687) in inode 21260.  IGNORED.
Illegal block #2 (2020565625) in inode 21260.  IGNORED.
Illegal block #3 (1936682542) in inode 21260.  IGNORED.
Illegal block #4 (6580597) in inode 21260.  IGNORED.
Inode 21261 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21261.  IGNORED.
Illegal block #1 (1937072687) in inode 21261.  IGNORED.
Illegal block #2 (2020565625) in inode 21261.  IGNORED.
Illegal block #3 (1936682542) in inode 21261.  IGNORED.
Illegal block #4 (6580597) in inode 21261.  IGNORED.
Inode 21262 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21262.  IGNORED.
Illegal block #1 (1937072687) in inode 21262.  IGNORED.
Illegal block #2 (2020565625) in inode 21262.  IGNORED.
Illegal block #3 (1936682542) in inode 21262.  IGNORED.
Illegal block #4 (6580597) in inode 21262.  IGNORED.
Inode 21263 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21263.  IGNORED.
Illegal block #1 (1701667887) in inode 21263.  IGNORED.
Illegal block #2 (1965975411) in inode 21263.  IGNORED.
Illegal block #3 (762079604) in inode 21263.  IGNORED.
Illegal block #4 (1970170220) in inode 21263.  IGNORED.
Inode 21263, i_size is 21, should be 24576.  Fix? no

Inode 21263, i_blocks is 0, should be 8.  Fix? no

Inode 21264 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21264.  IGNORED.
Illegal block #1 (1937072687) in inode 21264.  IGNORED.
Illegal block #2 (2020565625) in inode 21264.  IGNORED.
Illegal block #3 (1936682542) in inode 21264.  IGNORED.
Illegal block #4 (6580597) in inode 21264.  IGNORED.
Inode 21266 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21266.  IGNORED.
Illegal block #1 (1937072687) in inode 21266.  IGNORED.
Illegal block #2 (2020565625) in inode 21266.  IGNORED.
Illegal block #3 (1769304878) in inode 21266.  IGNORED.
Inode 21266, i_size is 17, should be 20480.  Fix? no

Inode 21266, i_blocks is 0, should be 8.  Fix? no

Inode 21269 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21269.  IGNORED.
Illegal block #1 (1818848047) in inode 21269.  IGNORED.
Illegal block #2 (1953836652) in inode 21269.  IGNORED.
Illegal block #3 (1814916201) in inode 21269.  IGNORED.
Illegal block #4 (2020961897) in inode 21269.  IGNORED.
Inode 21270 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21270.  IGNORED.
Illegal block #1 (1869444399) in inode 21270.  IGNORED.
Illegal block #2 (779382389) in inode 21270.  IGNORED.
Illegal block #3 (1818850421) in inode 21270.  IGNORED.
Illegal block #4 (1852402733) in inode 21270.  IGNORED.
Inode 21270, i_size is 22, should be 24576.  Fix? no

Inode 21270, i_blocks is 0, should be 8.  Fix? no

Inode 21271 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21271.  IGNORED.
Illegal block #1 (1937072687) in inode 21271.  IGNORED.
Illegal block #2 (2020565625) in inode 21271.  IGNORED.
Illegal block #3 (1936682542) in inode 21271.  IGNORED.
Illegal block #4 (6580597) in inode 21271.  IGNORED.
Inode 21272 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21272.  IGNORED.
Illegal block #1 (1701996335) in inode 21272.  IGNORED.
Illegal block #2 (1919364720) in inode 21272.  IGNORED.
Inode 21272, i_size is 14, should be 16384.  Fix? no

Inode 21272, i_blocks is 0, should be 8.  Fix? no

Inode 21273 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21273.  IGNORED.
Illegal block #1 (1937072687) in inode 21273.  IGNORED.
Illegal block #2 (2020565625) in inode 21273.  IGNORED.
Illegal block #3 (1936682542) in inode 21273.  IGNORED.
Illegal block #4 (6580597) in inode 21273.  IGNORED.
Inode 21274 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21274.  IGNORED.
Illegal block #1 (1937072687) in inode 21274.  IGNORED.
Illegal block #2 (2020565625) in inode 21274.  IGNORED.
Illegal block #3 (1769304878) in inode 21274.  IGNORED.
Inode 21274, i_size is 17, should be 20480.  Fix? no

Inode 21274, i_blocks is 0, should be 8.  Fix? no

Inode 21275 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21275.  IGNORED.
Illegal block #1 (1937072687) in inode 21275.  IGNORED.
Illegal block #2 (2020565625) in inode 21275.  IGNORED.
Illegal block #3 (1936682542) in inode 21275.  IGNORED.
Illegal block #4 (6580597) in inode 21275.  IGNORED.
Inode 21276 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21276.  IGNORED.
Illegal block #1 (1937072687) in inode 21276.  IGNORED.
Illegal block #2 (2020565625) in inode 21276.  IGNORED.
Illegal block #3 (1936682542) in inode 21276.  IGNORED.
Illegal block #4 (6580597) in inode 21276.  IGNORED.
Inode 21277 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21277.  IGNORED.
Illegal block #1 (1937072687) in inode 21277.  IGNORED.
Illegal block #2 (2020565625) in inode 21277.  IGNORED.
Illegal block #3 (1936682542) in inode 21277.  IGNORED.
Illegal block #4 (6580597) in inode 21277.  IGNORED.
Inode 21278 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21278.  IGNORED.
Illegal block #1 (1937072687) in inode 21278.  IGNORED.
Illegal block #2 (2020565625) in inode 21278.  IGNORED.
Illegal block #3 (1936682542) in inode 21278.  IGNORED.
Illegal block #4 (6580597) in inode 21278.  IGNORED.
Inode 21279 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21279.  IGNORED.
Illegal block #1 (1937072687) in inode 21279.  IGNORED.
Illegal block #2 (2020565625) in inode 21279.  IGNORED.
Illegal block #3 (1936682542) in inode 21279.  IGNORED.
Illegal block #4 (6580597) in inode 21279.  IGNORED.
Inode 21280 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21280.  IGNORED.
Illegal block #1 (1919378735) in inode 21280.  IGNORED.
Illegal block #2 (1731096677) in inode 21280.  IGNORED.
Illegal block #3 (7366002) in inode 21280.  IGNORED.
Inode 21281 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21281.  IGNORED.
Illegal block #1 (1937072687) in inode 21281.  IGNORED.
Illegal block #2 (2020565625) in inode 21281.  IGNORED.
Illegal block #3 (1936682542) in inode 21281.  IGNORED.
Illegal block #4 (6580597) in inode 21281.  IGNORED.
Inode 21282 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21282.  IGNORED.
Illegal block #1 (1937072687) in inode 21282.  IGNORED.
Illegal block #2 (2020565625) in inode 21282.  IGNORED.
Illegal block #3 (1936682542) in inode 21282.  IGNORED.
Illegal block #4 (6580597) in inode 21282.  IGNORED.
Inode 21284 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21284.  IGNORED.
Illegal block #1 (1970236719) in inode 21284.  IGNORED.
Illegal block #2 (1869640814) in inode 21284.  IGNORED.
Illegal block #3 (779382377) in inode 21284.  IGNORED.
Illegal block #4 (1987279219) in inode 21284.  IGNORED.
Illegal block #5 (1953066601) in inode 21284.  IGNORED.
Inode 21285 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21285.  IGNORED.
Illegal block #1 (1937072687) in inode 21285.  IGNORED.
Illegal block #2 (2020565625) in inode 21285.  IGNORED.
Illegal block #3 (1936682542) in inode 21285.  IGNORED.
Illegal block #4 (6580597) in inode 21285.  IGNORED.
Inode 21286 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21286.  IGNORED.
Illegal block #1 (1735355439) in inode 21286.  IGNORED.
Illegal block #2 (1932422761) in inode 21286.  IGNORED.
Illegal block #3 (1868849512) in inode 21286.  IGNORED.
Inode 21286, i_size is 17, should be 20480.  Fix? no

Inode 21286, i_blocks is 0, should be 8.  Fix? no

Inode 21288 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21288.  IGNORED.
Illegal block #1 (1937072687) in inode 21288.  IGNORED.
Illegal block #2 (2020565625) in inode 21288.  IGNORED.
Illegal block #3 (1936682542) in inode 21288.  IGNORED.
Illegal block #4 (6580597) in inode 21288.  IGNORED.
Inode 21289 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21289.  IGNORED.
Illegal block #1 (1937072687) in inode 21289.  IGNORED.
Illegal block #2 (2020565625) in inode 21289.  IGNORED.
Illegal block #3 (1936682542) in inode 21289.  IGNORED.
Illegal block #4 (6580597) in inode 21289.  IGNORED.
Inode 21291 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21291.  IGNORED.
Illegal block #1 (1937072687) in inode 21291.  IGNORED.
Illegal block #2 (2020565625) in inode 21291.  IGNORED.
Illegal block #3 (1936682542) in inode 21291.  IGNORED.
Illegal block #4 (6580597) in inode 21291.  IGNORED.
Inode 21292 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21292.  IGNORED.
Illegal block #1 (1937072687) in inode 21292.  IGNORED.
Illegal block #2 (2020565625) in inode 21292.  IGNORED.
Illegal block #3 (1936682542) in inode 21292.  IGNORED.
Illegal block #4 (6580597) in inode 21292.  IGNORED.
Inode 21294 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21294.  IGNORED.
Illegal block #1 (1937072687) in inode 21294.  IGNORED.
Illegal block #2 (2020565625) in inode 21294.  IGNORED.
Illegal block #3 (1936682542) in inode 21294.  IGNORED.
Illegal block #4 (6580597) in inode 21294.  IGNORED.
Inode 21295 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21295.  IGNORED.
Illegal block #1 (1937072687) in inode 21295.  IGNORED.
Illegal block #2 (2020565625) in inode 21295.  IGNORED.
Illegal block #3 (1936682542) in inode 21295.  IGNORED.
Illegal block #4 (6580597) in inode 21295.  IGNORED.
Inode 21296 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21296.  IGNORED.
Illegal block #1 (1937072687) in inode 21296.  IGNORED.
Illegal block #2 (2020565625) in inode 21296.  IGNORED.
Illegal block #3 (1936682542) in inode 21296.  IGNORED.
Illegal block #4 (6580597) in inode 21296.  IGNORED.
Inode 21299 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21299.  IGNORED.
Illegal block #1 (1937072687) in inode 21299.  IGNORED.
Illegal block #2 (2020565625) in inode 21299.  IGNORED.
Illegal block #3 (1936682542) in inode 21299.  IGNORED.
Illegal block #4 (6580597) in inode 21299.  IGNORED.
Inode 21300 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21300.  IGNORED.
Illegal block #1 (1684631599) in inode 21300.  IGNORED.
Illegal block #2 (1932420719) in inode 21300.  IGNORED.
Illegal block #3 (1769370489) in inode 21300.  IGNORED.
Illegal block #4 (7629166) in inode 21300.  IGNORED.
Inode 21301 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21301.  IGNORED.
Illegal block #1 (1937072687) in inode 21301.  IGNORED.
Illegal block #2 (2020565625) in inode 21301.  IGNORED.
Illegal block #3 (1936682542) in inode 21301.  IGNORED.
Illegal block #4 (6580597) in inode 21301.  IGNORED.
Inode 21303 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21303.  IGNORED.
Illegal block #1 (1836280879) in inode 21303.  IGNORED.
Illegal block #2 (1798202479) in inode 21303.  IGNORED.
Illegal block #3 (6582125) in inode 21303.  IGNORED.
Inode 21304 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21304.  IGNORED.
Illegal block #1 (1970236719) in inode 21304.  IGNORED.
Illegal block #2 (1965978734) in inode 21304.  IGNORED.
Illegal block #3 (762079604) in inode 21304.  IGNORED.
Illegal block #4 (1970170220) in inode 21304.  IGNORED.
Inode 21304, i_size is 21, should be 24576.  Fix? no

Inode 21304, i_blocks is 0, should be 8.  Fix? no

Inode 21306 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21306.  IGNORED.
Illegal block #1 (1937072687) in inode 21306.  IGNORED.
Illegal block #2 (2020565625) in inode 21306.  IGNORED.
Illegal block #3 (1936682542) in inode 21306.  IGNORED.
Illegal block #4 (6580597) in inode 21306.  IGNORED.
Inode 21307 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21307.  IGNORED.
Illegal block #1 (1937072687) in inode 21307.  IGNORED.
Illegal block #2 (2020565625) in inode 21307.  IGNORED.
Illegal block #3 (1936682542) in inode 21307.  IGNORED.
Illegal block #4 (6580597) in inode 21307.  IGNORED.
Inode 21308 has illegal block(s).  Clear? no

Illegal block #0 (1920169263) in inode 21308.  IGNORED.
Illegal block #1 (1852400175) in inode 21308.  IGNORED.
Illegal block #2 (1835628079) in inode 21308.  IGNORED.
Inode 21309 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21309.  IGNORED.
Illegal block #1 (1937072687) in inode 21309.  IGNORED.
Illegal block #2 (2020565625) in inode 21309.  IGNORED.
Illegal block #3 (1936682542) in inode 21309.  IGNORED.
Illegal block #4 (6580597) in inode 21309.  IGNORED.
Inode 21310 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21310.  IGNORED.
Illegal block #1 (1937072687) in inode 21310.  IGNORED.
Illegal block #2 (2020565625) in inode 21310.  IGNORED.
Illegal block #3 (1936682542) in inode 21310.  IGNORED.
Illegal block #4 (6580597) in inode 21310.  IGNORED.
Inode 21311 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21311.  IGNORED.
Illegal block #1 (1937072687) in inode 21311.  IGNORED.
Illegal block #2 (2020565625) in inode 21311.  IGNORED.
Illegal block #3 (1936682542) in inode 21311.  IGNORED.
Illegal block #4 (6580597) in inode 21311.  IGNORED.
Inode 21312 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21312.  IGNORED.
Illegal block #1 (1937072687) in inode 21312.  IGNORED.
Illegal block #2 (2020565625) in inode 21312.  IGNORED.
Illegal block #3 (1936682542) in inode 21312.  IGNORED.
Illegal block #4 (6580597) in inode 21312.  IGNORED.
Inode 21313 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21313.  IGNORED.
Illegal block #1 (1937072687) in inode 21313.  IGNORED.
Illegal block #2 (2020565625) in inode 21313.  IGNORED.
Illegal block #3 (1936682542) in inode 21313.  IGNORED.
Illegal block #4 (6580597) in inode 21313.  IGNORED.
Inode 21315 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21315.  IGNORED.
Illegal block #1 (1937072687) in inode 21315.  IGNORED.
Illegal block #2 (2020565625) in inode 21315.  IGNORED.
Illegal block #3 (1936682542) in inode 21315.  IGNORED.
Illegal block #4 (6580597) in inode 21315.  IGNORED.
Inode 21317 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21317.  IGNORED.
Illegal block #1 (1937072687) in inode 21317.  IGNORED.
Illegal block #2 (2020565625) in inode 21317.  IGNORED.
Illegal block #3 (1936682542) in inode 21317.  IGNORED.
Illegal block #4 (6580597) in inode 21317.  IGNORED.
Inode 21319 has illegal block(s).  Clear? no

Illegal block #0 (1920169263) in inode 21319.  IGNORED.
Illegal block #1 (1852400175) in inode 21319.  IGNORED.
Illegal block #2 (1952802607) in inode 21319.  IGNORED.
Illegal block #3 (7630959) in inode 21319.  IGNORED.
Inode 21320 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21320.  IGNORED.
Illegal block #1 (1937072687) in inode 21320.  IGNORED.
Illegal block #2 (2020565625) in inode 21320.  IGNORED.
Illegal block #3 (1936682542) in inode 21320.  IGNORED.
Illegal block #4 (6580597) in inode 21320.  IGNORED.
Inode 21322 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21322.  IGNORED.
Illegal block #1 (1937072687) in inode 21322.  IGNORED.
Illegal block #2 (2020565625) in inode 21322.  IGNORED.
Illegal block #3 (1936682542) in inode 21322.  IGNORED.
Illegal block #4 (6580597) in inode 21322.  IGNORED.
Inode 21323 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21323.  IGNORED.
Illegal block #1 (1919378991) in inode 21323.  IGNORED.
Illegal block #2 (1731096677) in inode 21323.  IGNORED.
Illegal block #3 (7366002) in inode 21323.  IGNORED.
Inode 21324 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21324.  IGNORED.
Illegal block #1 (1935761967) in inode 21324.  IGNORED.
Inode 21324, i_size is 9, should be 12288.  Fix? no

Inode 21324, i_blocks is 0, should be 8.  Fix? no

Inode 21325 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21325.  IGNORED.
Illegal block #1 (1937072687) in inode 21325.  IGNORED.
Illegal block #2 (2020565625) in inode 21325.  IGNORED.
Illegal block #3 (1936682542) in inode 21325.  IGNORED.
Illegal block #4 (6580597) in inode 21325.  IGNORED.
Inode 21327 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21327.  IGNORED.
Illegal block #1 (779449135) in inode 21327.  IGNORED.
Illegal block #2 (1684105331) in inode 21327.  IGNORED.
Inode 21327, i_size is 14, should be 16384.  Fix? no

Inode 21327, i_blocks is 0, should be 8.  Fix? no

Inode 21328 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21328.  IGNORED.
Illegal block #1 (1684370223) in inode 21328.  IGNORED.
Illegal block #2 (1684370222) in inode 21328.  IGNORED.
Inode 21329 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21329.  IGNORED.
Illegal block #1 (1937072687) in inode 21329.  IGNORED.
Illegal block #2 (2020565625) in inode 21329.  IGNORED.
Illegal block #3 (1936682542) in inode 21329.  IGNORED.
Illegal block #4 (6580597) in inode 21329.  IGNORED.
Inode 21330 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21330.  IGNORED.
Illegal block #1 (1937072687) in inode 21330.  IGNORED.
Illegal block #2 (2020565625) in inode 21330.  IGNORED.
Illegal block #3 (1936682542) in inode 21330.  IGNORED.
Illegal block #4 (6580597) in inode 21330.  IGNORED.
Inode 21331 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21331.  IGNORED.
Illegal block #1 (1937072687) in inode 21331.  IGNORED.
Illegal block #2 (2020565625) in inode 21331.  IGNORED.
Illegal block #3 (1936682542) in inode 21331.  IGNORED.
Illegal block #4 (6580597) in inode 21331.  IGNORED.
Inode 21332 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21332.  IGNORED.
Illegal block #1 (1769353070) in inode 21332.  IGNORED.
Illegal block #2 (1932423783) in inode 21332.  IGNORED.
Illegal block #3 (1868849512) in inode 21332.  IGNORED.
Inode 21332, i_size is 17, should be 20480.  Fix? no

Inode 21332, i_blocks is 0, should be 8.  Fix? no

Inode 21333 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21333.  IGNORED.
Illegal block #1 (1937072687) in inode 21333.  IGNORED.
Illegal block #2 (2020565625) in inode 21333.  IGNORED.
Illegal block #3 (1936682542) in inode 21333.  IGNORED.
Illegal block #4 (6580597) in inode 21333.  IGNORED.
Inode 21335 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21335.  IGNORED.
Illegal block #1 (1852387182) in inode 21335.  IGNORED.
Illegal block #2 (1685024115) in inode 21335.  IGNORED.
Illegal block #3 (1869441838) in inode 21335.  IGNORED.
Inode 21335, i_size is 17, should be 20480.  Fix? no

Inode 21335, i_blocks is 0, should be 8.  Fix? no

Inode 21336 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21336.  IGNORED.
Illegal block #1 (1701982062) in inode 21336.  IGNORED.
Illegal block #2 (1953460066) in inode 21336.  IGNORED.
Illegal block #3 (1937339182) in inode 21336.  IGNORED.
Illegal block #4 (1768843638) in inode 21336.  IGNORED.
Inode 21336, i_size is 21, should be 24576.  Fix? no

Inode 21336, i_blocks is 0, should be 8.  Fix? no

Inode 21337 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21337.  IGNORED.
Illegal block #1 (1937072687) in inode 21337.  IGNORED.
Illegal block #2 (2020565625) in inode 21337.  IGNORED.
Illegal block #3 (1936682542) in inode 21337.  IGNORED.
Illegal block #4 (6580597) in inode 21337.  IGNORED.
Inode 21339 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21339.  IGNORED.
Illegal block #1 (1769353070) in inode 21339.  IGNORED.
Illegal block #2 (1932425072) in inode 21339.  IGNORED.
Illegal block #3 (1868849512) in inode 21339.  IGNORED.
Inode 21339, i_size is 17, should be 20480.  Fix? no

Inode 21339, i_blocks is 0, should be 8.  Fix? no

Inode 21341 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21341.  IGNORED.
Illegal block #1 (1937072687) in inode 21341.  IGNORED.
Illegal block #2 (2020565625) in inode 21341.  IGNORED.
Illegal block #3 (1936682542) in inode 21341.  IGNORED.
Illegal block #4 (6580597) in inode 21341.  IGNORED.
Inode 21342 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21342.  IGNORED.
Illegal block #1 (1869426542) in inode 21342.  IGNORED.
Illegal block #2 (1718511972) in inode 21342.  IGNORED.
Illegal block #3 (1835740783) in inode 21342.  IGNORED.
Inode 21342, i_size is 18, should be 20480.  Fix? no

Inode 21342, i_blocks is 0, should be 8.  Fix? no

Inode 21346 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21346.  IGNORED.
Illegal block #1 (1684418414) in inode 21346.  IGNORED.
Illegal block #2 (778793833) in inode 21346.  IGNORED.
Illegal block #3 (1818850421) in inode 21346.  IGNORED.
Illegal block #4 (1852402733) in inode 21346.  IGNORED.
Inode 21346, i_size is 22, should be 24576.  Fix? no

Inode 21346, i_blocks is 0, should be 8.  Fix? no

Inode 21347 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21347.  IGNORED.
Illegal block #1 (1869426542) in inode 21347.  IGNORED.
Illegal block #2 (1869770852) in inode 21347.  IGNORED.
Illegal block #3 (1798202722) in inode 21347.  IGNORED.
Illegal block #4 (6582125) in inode 21347.  IGNORED.
Inode 21352 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21352.  IGNORED.
Illegal block #1 (1869361006) in inode 21352.  IGNORED.
Illegal block #2 (1970562419) in inode 21352.  IGNORED.
Illegal block #3 (1953836656) in inode 21352.  IGNORED.
Illegal block #4 (1814916201) in inode 21352.  IGNORED.
Illegal block #5 (2020961897) in inode 21352.  IGNORED.
Inode 21355 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21355.  IGNORED.
Illegal block #1 (1701064558) in inode 21355.  IGNORED.
Illegal block #2 (1685024112) in inode 21355.  IGNORED.
Illegal block #3 (1869441838) in inode 21355.  IGNORED.
Inode 21355, i_size is 17, should be 20480.  Fix? no

Inode 21355, i_blocks is 0, should be 8.  Fix? no

Inode 21358 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21358.  IGNORED.
Illegal block #1 (1836199790) in inode 21358.  IGNORED.
Illegal block #2 (778334061) in inode 21358.  IGNORED.
Illegal block #3 (1685024107) in inode 21358.  IGNORED.
Inode 21360 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21360.  IGNORED.
Illegal block #1 (1937072687) in inode 21360.  IGNORED.
Illegal block #2 (2020565625) in inode 21360.  IGNORED.
Illegal block #3 (1936682542) in inode 21360.  IGNORED.
Illegal block #4 (6580597) in inode 21360.  IGNORED.
Inode 21362 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21362.  IGNORED.
Illegal block #1 (1970417518) in inode 21362.  IGNORED.
Illegal block #2 (1986358382) in inode 21362.  IGNORED.
Illegal block #3 (1932422245) in inode 21362.  IGNORED.
Illegal block #4 (1769370489) in inode 21362.  IGNORED.
Illegal block #5 (7629166) in inode 21362.  IGNORED.
Inode 21363 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21363.  IGNORED.
Illegal block #1 (1752379246) in inode 21363.  IGNORED.
Illegal block #2 (1868854389) in inode 21363.  IGNORED.
Illegal block #3 (1932422775) in inode 21363.  IGNORED.
Illegal block #4 (1769370489) in inode 21363.  IGNORED.
Illegal block #5 (7629166) in inode 21363.  IGNORED.
Inode 21367 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21367.  IGNORED.
Illegal block #1 (1937072687) in inode 21367.  IGNORED.
Illegal block #2 (2020565625) in inode 21367.  IGNORED.
Illegal block #3 (1936682542) in inode 21367.  IGNORED.
Illegal block #4 (6580597) in inode 21367.  IGNORED.
Inode 21368 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21368.  IGNORED.
Illegal block #1 (1937072687) in inode 21368.  IGNORED.
Illegal block #2 (2020565625) in inode 21368.  IGNORED.
Illegal block #3 (1936682542) in inode 21368.  IGNORED.
Illegal block #4 (6580597) in inode 21368.  IGNORED.
Inode 21370 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21370.  IGNORED.
Illegal block #1 (1937072687) in inode 21370.  IGNORED.
Illegal block #2 (2020565625) in inode 21370.  IGNORED.
Illegal block #3 (1936682542) in inode 21370.  IGNORED.
Illegal block #4 (6580597) in inode 21370.  IGNORED.
Inode 21371 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21371.  IGNORED.
Illegal block #1 (1937072687) in inode 21371.  IGNORED.
Illegal block #2 (2020565625) in inode 21371.  IGNORED.
Illegal block #3 (1936682542) in inode 21371.  IGNORED.
Illegal block #4 (6580597) in inode 21371.  IGNORED.
Inode 21373 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21373.  IGNORED.
Illegal block #1 (1937072687) in inode 21373.  IGNORED.
Illegal block #2 (2020565625) in inode 21373.  IGNORED.
Illegal block #3 (1936682542) in inode 21373.  IGNORED.
Illegal block #4 (6580597) in inode 21373.  IGNORED.
Inode 21374 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21374.  IGNORED.
Illegal block #1 (1818373998) in inode 21374.  IGNORED.
Illegal block #2 (1684759407) in inode 21374.  IGNORED.
Illegal block #3 (1965979237) in inode 21374.  IGNORED.
Illegal block #4 (762079604) in inode 21374.  IGNORED.
Illegal block #5 (1970170220) in inode 21374.  IGNORED.
Inode 21374, i_size is 25, should be 28672.  Fix? no

Inode 21374, i_blocks is 0, should be 8.  Fix? no

Inode 21375 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21375.  IGNORED.
Illegal block #1 (1634217838) in inode 21375.  IGNORED.
Illegal block #2 (1932424300) in inode 21375.  IGNORED.
Illegal block #3 (1769370489) in inode 21375.  IGNORED.
Illegal block #4 (7629166) in inode 21375.  IGNORED.
Inode 21377 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21377.  IGNORED.
Illegal block #1 (1937072687) in inode 21377.  IGNORED.
Illegal block #2 (2020565625) in inode 21377.  IGNORED.
Illegal block #3 (1936682542) in inode 21377.  IGNORED.
Illegal block #4 (6580597) in inode 21377.  IGNORED.
Inode 21381 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21381.  IGNORED.
Illegal block #1 (1937072687) in inode 21381.  IGNORED.
Illegal block #2 (2020565625) in inode 21381.  IGNORED.
Illegal block #3 (1936682542) in inode 21381.  IGNORED.
Illegal block #4 (6580597) in inode 21381.  IGNORED.
Inode 21382 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21382.  IGNORED.
Illegal block #1 (1802317678) in inode 21382.  IGNORED.
Illegal block #2 (1885435763) in inode 21382.  IGNORED.
Illegal block #3 (1769239854) in inode 21382.  IGNORED.
Illegal block #4 (1768697196) in inode 21382.  IGNORED.
Illegal block #5 (7894382) in inode 21382.  IGNORED.
Inode 21384 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21384.  IGNORED.
Illegal block #1 (2004037486) in inode 21384.  IGNORED.
Illegal block #2 (1718579297) in inode 21384.  IGNORED.
Illegal block #3 (1953836646) in inode 21384.  IGNORED.
Illegal block #4 (1814916201) in inode 21384.  IGNORED.
Illegal block #5 (2020961897) in inode 21384.  IGNORED.
Inode 21385 is a zero-length directory.  Clear? no

Inode 21385, i_size is 613684, should be 0.  Fix? no

Inode 21388 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21388.  IGNORED.
Illegal block #1 (1937072687) in inode 21388.  IGNORED.
Illegal block #2 (2020565625) in inode 21388.  IGNORED.
Illegal block #3 (1936682542) in inode 21388.  IGNORED.
Illegal block #4 (6580597) in inode 21388.  IGNORED.
Inode 21390 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21390.  IGNORED.
Illegal block #1 (1937072687) in inode 21390.  IGNORED.
Illegal block #2 (2020565625) in inode 21390.  IGNORED.
Illegal block #3 (1936682542) in inode 21390.  IGNORED.
Illegal block #4 (6580597) in inode 21390.  IGNORED.
Inode 21392 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21392.  IGNORED.
Illegal block #1 (1802317678) in inode 21392.  IGNORED.
Illegal block #2 (1831760742) in inode 21392.  IGNORED.
Illegal block #3 (2020175465) in inode 21392.  IGNORED.
Illegal block #4 (1769239854) in inode 21392.  IGNORED.
Illegal block #5 (1768697196) in inode 21392.  IGNORED.
Illegal block #6 (7894382) in inode 21392.  IGNORED.
Inode 21398 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21398.  IGNORED.
Illegal block #1 (1852387182) in inode 21398.  IGNORED.
Illegal block #2 (1932424297) in inode 21398.  IGNORED.
Illegal block #3 (1769370489) in inode 21398.  IGNORED.
Illegal block #4 (7629166) in inode 21398.  IGNORED.
Inode 21399 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21399.  IGNORED.
Illegal block #1 (1768959854) in inode 21399.  IGNORED.
Illegal block #2 (1601466230) in inode 21399.  IGNORED.
Illegal block #3 (1953460082) in inode 21399.  IGNORED.
Illegal block #4 (1769239854) in inode 21399.  IGNORED.
Illegal block #5 (1768697196) in inode 21399.  IGNORED.
Illegal block #6 (7894382) in inode 21399.  IGNORED.
Inode 21404 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21404.  IGNORED.
Illegal block #1 (2004037486) in inode 21404.  IGNORED.
Illegal block #2 (1852797025) in inode 21404.  IGNORED.
Illegal block #3 (1769239854) in inode 21404.  IGNORED.
Illegal block #4 (1768697196) in inode 21404.  IGNORED.
Illegal block #5 (7894382) in inode 21404.  IGNORED.
Inode 21405 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21405.  IGNORED.
Illegal block #1 (1937072687) in inode 21405.  IGNORED.
Illegal block #2 (2020565625) in inode 21405.  IGNORED.
Illegal block #3 (1936682542) in inode 21405.  IGNORED.
Illegal block #4 (6580597) in inode 21405.  IGNORED.
Inode 21406 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21406.  IGNORED.
Illegal block #1 (1937072687) in inode 21406.  IGNORED.
Illegal block #2 (2020565625) in inode 21406.  IGNORED.
Illegal block #3 (1936682542) in inode 21406.  IGNORED.
Illegal block #4 (6580597) in inode 21406.  IGNORED.
Inode 21408 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21408.  IGNORED.
Illegal block #1 (1937072687) in inode 21408.  IGNORED.
Illegal block #2 (2020565625) in inode 21408.  IGNORED.
Illegal block #3 (1936682542) in inode 21408.  IGNORED.
Illegal block #4 (6580597) in inode 21408.  IGNORED.
Inode 21410 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21410.  IGNORED.
Illegal block #1 (1701982062) in inode 21410.  IGNORED.
Illegal block #2 (1919968353) in inode 21410.  IGNORED.
Illegal block #3 (1818846831) in inode 21410.  IGNORED.
Illegal block #4 (1953836645) in inode 21410.  IGNORED.
Illegal block #5 (1814916201) in inode 21410.  IGNORED.
Illegal block #6 (2020961897) in inode 21410.  IGNORED.
Inode 21413 has illegal block(s).  Clear? no

Illegal block #0 (1768059695) in inode 21413.  IGNORED.
Illegal block #1 (1869623150) in inode 21413.  IGNORED.
Illegal block #2 (1869768055) in inode 21413.  IGNORED.
Illegal block #3 (1932420710) in inode 21413.  IGNORED.
Illegal block #4 (1769370489) in inode 21413.  IGNORED.
Illegal block #5 (7629166) in inode 21413.  IGNORED.
Inode 21414 has illegal block(s).  Clear? no

Illegal block #0 (1852400175) in inode 21414.  IGNORED.
Illegal block #1 (1937072687) in inode 21414.  IGNORED.
Illegal block #2 (2020565625) in inode 21414.  IGNORED.
Illegal block #3 (1936682542) in inode 21414.  IGNORED.
Illegal block #4 (6580597) in inode 21414.  IGNORED.
Inode 21422 has illegal block(s).  Clear? no

Illegal block #0 (1634496374) in inode 21422.  IGNORED.
Illegal block #1 (1701603700) in inode 21422.  IGNORED.
Illegal block #2 (1886221359) in inode 21422.  IGNORED.
Inode 21422 is a zero-length directory.  Clear? no

Inode 21422, i_size is 12, should be 0.  Fix? no


Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 8102: 25711
Multiply-claimed block(s) in inode 8477: 28773
Multiply-claimed block(s) in inode 8624: 30575
Multiply-claimed block(s) in inode 8642: 30837
Multiply-claimed block(s) in inode 21263: 120
Multiply-claimed block(s) in inode 21266: 100
Multiply-claimed block(s) in inode 21270: 30837
Multiply-claimed block(s) in inode 21272: 28773
Multiply-claimed block(s) in inode 21274: 100
Multiply-claimed block(s) in inode 21286: 119
Multiply-claimed block(s) in inode 21304: 120
Multiply-claimed block(s) in inode 21324: 104
Multiply-claimed block(s) in inode 21327: 30575
Multiply-claimed block(s) in inode 21332: 119
Multiply-claimed block(s) in inode 21335: 100
Multiply-claimed block(s) in inode 21336: 116
Multiply-claimed block(s) in inode 21339: 119
Multiply-claimed block(s) in inode 21342: 25711
Multiply-claimed block(s) in inode 21346: 30837
Multiply-claimed block(s) in inode 21355: 100
Multiply-claimed block(s) in inode 21374: 120
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 21 inodes containing multiply-claimed blocks.)

File /usr/include/ogg (inode #8102, mod time Wed Nov 27 17:03:57 2013) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	/modinfo (inode #21342, mod time Wed Nov 27 17:05:09 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /usr/bin/dbus-daemon (inode #8477, mod time Wed Nov 27 17:03:59 2013) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	/grep (inode #21272, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /usr/bin/chage (inode #8624, mod time Wed Nov 27 17:03:59 2013) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	/su (inode #21327, mod time Wed Nov 27 17:05:09 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /usr/bin/udevadm (inode #8642, mod time Wed Nov 27 17:04:00 2013) 
  has 1 multiply-claimed block(s), shared with 2 file(s):
	/fdisk (inode #21346, mod time Wed Nov 27 17:05:09 2013)
	/umount (inode #21270, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /dmesg (inode #21263, mod time Wed Nov 27 17:05:08 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/blockdev (inode #21374, mod time Wed Nov 27 17:05:09 2013)
	/mount (inode #21304, mod time Wed Nov 27 17:05:09 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /ping6 (inode #21266, mod time Wed Nov 27 17:05:08 2013) 
  has 1 multiply-claimed block(s), shared with 4 file(s):
	<filesystem metadata>
	/depmod (inode #21355, mod time Wed Nov 27 17:05:09 2013)
	/insmod (inode #21335, mod time Wed Nov 27 17:05:09 2013)
	/ping (inode #21274, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /umount (inode #21270, mod time Wed Nov 27 17:05:08 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/fdisk (inode #21346, mod time Wed Nov 27 17:05:09 2013)
	/usr/bin/udevadm (inode #8642, mod time Wed Nov 27 17:04:00 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /grep (inode #21272, mod time Wed Nov 27 17:05:08 2013) 
  has 1 multiply-claimed block(s), shared with 2 file(s):
	<filesystem metadata>
	/usr/bin/dbus-daemon (inode #8477, mod time Wed Nov 27 17:03:59 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /ping (inode #21274, mod time Wed Nov 27 17:05:08 2013) 
  has 1 multiply-claimed block(s), shared with 4 file(s):
	<filesystem metadata>
	/depmod (inode #21355, mod time Wed Nov 27 17:05:09 2013)
	/insmod (inode #21335, mod time Wed Nov 27 17:05:09 2013)
	/ping6 (inode #21266, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /login (inode #21286, mod time Wed Nov 27 17:05:08 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/vipw (inode #21339, mod time Wed Nov 27 17:05:09 2013)
	/vigr (inode #21332, mod time Wed Nov 27 17:05:09 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /mount (inode #21304, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/blockdev (inode #21374, mod time Wed Nov 27 17:05:09 2013)
	/dmesg (inode #21263, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /sh (inode #21324, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	<filesystem metadata>
Clone multiply-claimed blocks? no

Delete file? no

File /su (inode #21327, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 2 file(s):
	<filesystem metadata>
	/usr/bin/chage (inode #8624, mod time Wed Nov 27 17:03:59 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /vigr (inode #21332, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/vipw (inode #21339, mod time Wed Nov 27 17:05:09 2013)
	/login (inode #21286, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /insmod (inode #21335, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 4 file(s):
	<filesystem metadata>
	/depmod (inode #21355, mod time Wed Nov 27 17:05:09 2013)
	/ping (inode #21274, mod time Wed Nov 27 17:05:08 2013)
	/ping6 (inode #21266, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /reboot (inode #21336, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 1 file(s):
	<filesystem metadata>
Clone multiply-claimed blocks? no

Delete file? no

File /vipw (inode #21339, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/vigr (inode #21332, mod time Wed Nov 27 17:05:09 2013)
	/login (inode #21286, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /modinfo (inode #21342, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 2 file(s):
	<filesystem metadata>
	/usr/include/ogg (inode #8102, mod time Wed Nov 27 17:03:57 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /fdisk (inode #21346, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/umount (inode #21270, mod time Wed Nov 27 17:05:08 2013)
	/usr/bin/udevadm (inode #8642, mod time Wed Nov 27 17:04:00 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /depmod (inode #21355, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 4 file(s):
	<filesystem metadata>
	/insmod (inode #21335, mod time Wed Nov 27 17:05:09 2013)
	/ping (inode #21274, mod time Wed Nov 27 17:05:08 2013)
	/ping6 (inode #21266, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

File /blockdev (inode #21374, mod time Wed Nov 27 17:05:09 2013) 
  has 1 multiply-claimed block(s), shared with 3 file(s):
	<filesystem metadata>
	/mount (inode #21304, mod time Wed Nov 27 17:05:09 2013)
	/dmesg (inode #21263, mod time Wed Nov 27 17:05:08 2013)
Clone multiply-claimed blocks? no

Delete file? no

Pass 2: Checking directory structure
Symlink /run (inode #77) is invalid.
Clear? no

Entry 'run' in / (2) has an incorrect filetype (was 2, should be 0).
Fix? no

Entry 'false' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'sleep' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'more' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'hostname' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'chattr' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ash' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'dmesg' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'cat' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ping6' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'kill' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'umount' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'chmod' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'grep' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'df' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ping' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'dd' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'cp' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'date' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mktemp' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'stty' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'egrep' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'rmdir' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ls' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mountpoint' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'gzip' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'login' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'gunzip' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'rm' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mknod' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'sync' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'zcat' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'pwd' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'uname' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ps' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'pidof' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'cpio' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'lsmod' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mount' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'chown' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'tar' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'vi' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'dumpkmap' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ln' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'true' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'netstat' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'usleep' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mkdir' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'touch' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'getopt' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mv' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'dnsdomainname' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'fgrep' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'sh' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'echo' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'su' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'sed' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'chgrp' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'fsck' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'route' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'vigr' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'start-stop-daemon' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'insmod' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'reboot' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'hwclock' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'vipw' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'logread' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'modinfo' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'fdisk' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'modprobe' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'losetup' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'depmod' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'rmmod' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ifconfig' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'runlevel' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'shutdown' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'sulogin' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'udhcpc' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'setconsole' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'loadkmap' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'syslogd' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'blockdev' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'halt' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ifup' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'klogd' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mkswap' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'swapoff' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ldconfig' in / (2) has an incorrect filetype (was 1, should be 2).
Fix? no

Entry 'fsck.minix' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'getty' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'mkfs.minix' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'init' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'pivot_root' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'swapon' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'sysctl' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'switch_root' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ifdown' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'readprofile' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'poweroff' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'ip' in / (2) has an incorrect filetype (was 7, should be 1).
Fix? no

Entry 'tmp' in / (2) has an incorrect filetype (was 7, should be 2).
Fix? no

Pass 3: Checking directory connectivity
'..' in /ldconfig (21385) is <The NULL inode> (0), should be / (2).
Fix? no

'..' in /tmp (21422) is <The NULL inode> (0), should be / (2).
Fix? no

Pass 4: Checking reference counts
Inode 2 ref count is 7, should be 6.  Fix? no

Inode 77 ref count is 2, should be 1.  Fix? no

Unattached inode 21488
Connect to /lost+found? no

Pass 5: Checking group summary information
Inode bitmap differences:  +21488
Fix? no

Directories count wrong for group #0 (658, counted=657).
Fix? no

Directories count wrong for group #1 (902, counted=904).
Fix? no


tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual.ext3: ********** WARNING: Filesystem still has errors **********

tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual.ext3: 21363/73280 files (0.1% non-contiguous), 111391/146432 blocks

[-- Attachment #3: todd-new.bb --]
[-- Type: application/octet-stream, Size: 502 bytes --]

require core-image-minimal-dev.bb

DESCRIPTION = "A small image just capable of allowing a device to boot and \
is suitable for development work."

IMAGE_FEATURES += " \
dev-pkgs \
package-management \
ssh-server-dropbear \
"

IMAGE_INSTALL += " \
bash \
gcc \
task-native-sdk \
connman \
opencv \
opencv-dev  \
pkgconfig \
gsl-dev \
grep \
git \
ncurses-dev \
python-argparse \
python-numpy \
python-pip \
python-pyserial \
opkg \
shadow-securetty \
vim \
rsync \
wpa-supplicant \
wireless-tools \
"

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Robert Yang]

Hi Todd,

I can reproduce the similar problem now, I think that it should be a
bug of e2fsprogs, it seems the debugfs can't know the free space
correctly, and thus it appears no free blocks, I'm sorry to say that
I can't fix it in a short while, but I will fix it in one or two weeks,
maybe you can set this in the local.conf as a workaround:

IMAGE_ROOTFS_EXTRA_SPACE = "51200"

If 51200 is not enough, it can be higher, the unit is Kbytes.


And the todd-new-wandboard-dual.tar.bz2 works well is because it doesn't
generated by debugfs.

// Robert

On 11/29/2013 12:02 AM, Todd Stellanova wrote:
> Thanks for taking a look at this Robert!
> Below is the ls output: fsck output and bb are attached.
>
> I should note that if I manually copy the bz2 output of bitbake to an
> sdcard, like:
> sudo tar xjvf
> tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual.tar.bz2 -C
> /media/rootfs
> the image boots fine and contains all the packages I expect.
>
> todd@ubuntu:~/proj/wandboard/fsl-community-bsp/build$ ls -stlh
> tmp/deploy/images/wandboard-dual/*.ext3
> 572M -rw-r--r-- 1 todd todd 572M Nov 27 17:05
> tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131128005017.rootfs.ext3
>     0 lrwxrwxrwx 1 todd todd   50 Nov 27 17:05
> tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual.ext3 ->
> todd-new-wandboard-dual-20131128005017.rootfs.ext3
> 435M -rw-r--r-- 1 todd todd 436M Nov 26 16:17
> tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131127001137.rootfs.ext3
> 435M -rw-r--r-- 1 todd todd 436M Nov 26 15:55
> tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131126234958.rootfs.ext3
> 435M -rw-r--r-- 1 todd todd 436M Nov 26 15:36
> tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131126232014.rootfs.ext3
> 435M -rw-r--r-- 1 todd todd 436M Nov 26 14:03
> tmp/deploy/images/wandboard-dual/todd-new-wandboard-dual-20131126161048.rootfs.ext3
>
>
>
>
> On Thu, Nov 28, 2013 at 4:48 AM, Robert Yang <liezhi.yang@windriver.com>wrote:
>
>>
>> Hi Todd,
>>
>> I can't reproduce the problem, the rpm has more space than ipk is because
>> of the IMAGE_ROOTFS_EXTRA_SPACE, which is 50M * 1.3 by default.
>>
>> Would you please try the following commands:
>>
>> 1) $ ls -stlh tmp/deploy/images/wandboard-dual/core-image-minimal-dev-
>> wandboard-dual-*.ext3
>>
>> 2) $ fsck.ext4 -fn /path/to/image.ext3
>>
>> And can you show the bb file if possible ?
>>
>> // Robert
>>
>>
>> On 11/27/2013 09:27 AM, Todd Stellanova wrote:
>>
>>> Tried creating a fresh build folder and giving the vm more ram but the
>>> results are basically the same:
>>>
>>> Allocated inode: 15264
>>> copy_file: Could not allocate block in ext2 filesystem
>>> debugfs: sif "libgio-2.0.so.0.3800.1" mode 0x81ed
>>>
>>> It appears that using package_rpm successfully allocates something like
>>> 15968 inodes. When calculating the ROOTFS_SIZE it looks like package_rpm
>>> and package_ipk are using very different values:
>>>
>>> package_rpm:
>>>
>>> ++ du -ks
>>> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-
>>> linux-gnueabi/todd-new/1.0-r0/rootfs
>>> ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size
>>> :
>>> 8192) + 0 + *51200*); if (base_size != int(base_size)) base_size =
>>>
>>> int(base_size + 1); base_size = base_size + 4096 - 1; base_size -=
>>> base_size % 4096; print base_size }'
>>>
>>> + ROOTFS_SIZE=*458752*
>>>
>>>
>>> package_ipk:
>>>
>>> ++ du -ks
>>> /fsl-community-bsp/build/tmp/work/wandboard_dual-poky-
>>> linux-gnueabi/todd-new/1.0-r0/rootfs
>>> ++ awk '{base_size = $1 * 1.3; base_size = ((base_size > 8192 ? base_size
>>> :
>>> 8192) + 0); if (base_size != int(base_size)) base_size = int(base_size +
>>> 1); base_size = base_size + 4096 - 1; base_size -= base_size % 4096; print
>>> base_size }'
>>>
>>> + ROOTFS_SIZE=*376832*
>>>
>>>
>>> I'm just guessing here, but it seems like package_ipk is underestimating
>>> ROOTFS_SIZE and subsequently populate-extfs.sh fails trying to add files
>>> to
>>> the ext fs.  Any ideas what might cause this?
>>>
>>> Thanks for any help!
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Nov 25, 2013 at 7:03 AM, Todd Stellanova <tstellanova@gmail.com
>>>> wrote:
>>>
>>>   Thanks for the ideas. I'll try creating a new build folder. If that still
>>>> shows the problem, I'm thinking this has something to do with the fact
>>>> that
>>>> I'm running the build inside a vm (inside an Ubuntu vm running on a Mac).
>>>> It looks like the build is using debugfs...maybe it's running out of ram
>>>> at
>>>> some point and not obtaining more in the vm properly?
>>>>
>>>>   On Nov 25, 2013, at 5:21 AM, Paul Eggleton <
>>>>>
>>>> paul.eggleton@linux.intel.com> wrote:
>>>>
>>>>>
>>>>> Hi Nicolas / Todd,
>>>>>
>>>>>   On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote:
>>>>>> On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova
>>>>>> <tstellanova@gmail.com>wrote:
>>>>>>
>>>>>>> It appears that copying the files to the ext3 / sdcard image is
>>>>>>>
>>>>>> failing in
>>>>
>>>>> *populate-extfs.sh*
>>>>>>> I see a series of these errors:
>>>>>>>
>>>>>>> *copy_file: Could not allocate block in ext2 filesystem*
>>>>>>>
>>>>>>> Any idea what might cause this?  I've verified that the initial .tar
>>>>>>> archive and the bz2 contain the right files.
>>>>>>>
>>>>>>
>>>>>> can you try to create a new <build> folder (do not remove the current
>>>>>>
>>>>> one
>>>>
>>>>> for now) and reuse the downloads and sstate folder? i am wondering if
>>>>>>
>>>>> there
>>>>
>>>>> is a bug when trying to change PACKAGE_CLASSES in an existing <build>
>>>>>> folder.
>>>>>>
>>>>>
>>>>> I do this not infrequently and never hit a problem like this, so I doubt
>>>>>
>>>> this
>>>>
>>>>> is the case.
>>>>>
>>>>> Either there is a problem in how the filesystem is being set up (block
>>>>>
>>>> sizes,
>>>>
>>>>> etc.) or there is some kind of corruption occurring.
>>>>>
>>>>> Cheers,
>>>>> Paul
>>>>>
>>>>> --
>>>>>
>>>>> Paul Eggleton
>>>>> Intel Open Source Technology Centre
>>>>>
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>

Re: unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

[Paul Eggleton]

Hi Robert,

On Friday 29 November 2013 15:28:28 Robert Yang wrote:
> I can reproduce the similar problem now, I think that it should be a
> bug of e2fsprogs, it seems the debugfs can't know the free space
> correctly, and thus it appears no free blocks, I'm sorry to say that
> I can't fix it in a short while, but I will fix it in one or two weeks,
> maybe you can set this in the local.conf as a workaround:
> 
> IMAGE_ROOTFS_EXTRA_SPACE = "51200"
> 
> If 51200 is not enough, it can be higher, the unit is Kbytes.

Thanks for looking into this. Would you mind entering a bug so we can track 
the issue?

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre