Patchwork [RFC,0/2] Fully support ext3/ext4 rootfs generation

login
register
mail settings
Submitter Robert Yang
Date March 2, 2013, 10:46 a.m.
Message ID <cover.1362217827.git.liezhi.yang@windriver.com>
Download mbox
Permalink /patch/45411/
State New
Headers show

Pull-request

git://git.pokylinux.org/poky-contrib robert/e2fsprogs

Comments

Robert Yang - March 2, 2013, 10:46 a.m.
Replace genext2fs with populate-extfs.sh in image_types.bbclass to fully
support ext3/ext4 rootfs.

Comments from Darren:
We used genext2fs to create ext3/ext4 rootfs in the past, basically,
genext2fs doesn't support creating ext4 filesystems. It creates, as I
understand it, an ext2 filesystem, then adds a journal, and sets some
bits. It can't support the newer features like extents. So what we end
up with is a bit of a hack for a filesystem.

The ext tools (e2fsprogs) unfortunately don't provide an integrated
solution for generating prepopulated filesystem images as many other
mkfs* tools do. One thing missing was symlink support in libext2fs. I
added that support and demonstrated a script which uses the e2fsprogs
debugfs tool that can populate the newly formatted filesystem from a
directory and without root privileges.

This patches integrate this stage of development into OE-Core. We can
go about this in two ways. One is to just prototype this in a branch and
use it to validate the functionality and not make any changes to oe-core
image generation until mke2fs has initial directory support. The other
is to merge this and get broader testing of the concept and later move
to the full mke2fs implementation once it becomes available. I
understand the resistance to the latter, but long term I think it will
result in a more robust solution as we will have caught more of the
corner cases and have been able to do a better job integrating into
mke2fs the first time.


* Impact:
  + Rootfs generation time:
    - For a core-image-minimal image, about more 3 seconds are needed
    - For a core-image-sato image, about more 15 seconds are needed

  + Disk space usage:
    - Nearly no changes:
    $ ls -lh BEFORE.rootfs.ext3 AFTER.rootfs.ext3 | awk '{print $5"\t"$NF}'
    357M BEFORE.rootfs.ext3
    357M AFTER.rootfs.ext3
    
    $ du -sh BEFORE.rootfs.ext3 AFTER.rootfs.ext3
    238M    BEFORE.rootfs.ext3
    357M    AFTER.rootfs.ext3
    # This is different because BEFORE.rootfs.ext3 has sparse files,
    # they are very similar (less than 1M gap) after mount them and run
    # "du -sh".

// Robert

The following changes since commit 8264863ea0674f6cb105f5f7301861408fdc409b:

  Add KERNEL_EXTRA_ARGS parameter (2013-03-01 14:57:52 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib robert/e2fsprogs
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/e2fsprogs

Robert Yang (2):
  e2fsprogs: add populate-extfs.sh
  image_types.bbclass: replace genext2fs with populate-extfs.sh

 meta/classes/image_types.bbclass                   | 45 ++++++--------
 .../e2fsprogs/e2fsprogs-1.42.7/populate-extfs.sh   | 69 ++++++++++++++++++++++
 .../recipes-devtools/e2fsprogs/e2fsprogs_1.42.7.bb |  2 +
 3 files changed, 88 insertions(+), 28 deletions(-)
 create mode 100644 meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.7/populate-extfs.sh
Richard Purdie - March 2, 2013, 11:39 a.m.
On Sat, 2013-03-02 at 18:46 +0800, Robert Yang wrote:
> Replace genext2fs with populate-extfs.sh in image_types.bbclass to fully
> support ext3/ext4 rootfs.
> 
> Comments from Darren:
> We used genext2fs to create ext3/ext4 rootfs in the past, basically,
> genext2fs doesn't support creating ext4 filesystems. It creates, as I
> understand it, an ext2 filesystem, then adds a journal, and sets some
> bits. It can't support the newer features like extents. So what we end
> up with is a bit of a hack for a filesystem.
> 
> The ext tools (e2fsprogs) unfortunately don't provide an integrated
> solution for generating prepopulated filesystem images as many other
> mkfs* tools do. One thing missing was symlink support in libext2fs. I
> added that support and demonstrated a script which uses the e2fsprogs
> debugfs tool that can populate the newly formatted filesystem from a
> directory and without root privileges.
> 
> This patches integrate this stage of development into OE-Core. We can
> go about this in two ways. One is to just prototype this in a branch and
> use it to validate the functionality and not make any changes to oe-core
> image generation until mke2fs has initial directory support. The other
> is to merge this and get broader testing of the concept and later move
> to the full mke2fs implementation once it becomes available. I
> understand the resistance to the latter, but long term I think it will
> result in a more robust solution as we will have caught more of the
> corner cases and have been able to do a better job integrating into
> mke2fs the first time.
> 
> 
> * Impact:
>   + Rootfs generation time:
>     - For a core-image-minimal image, about more 3 seconds are needed
>     - For a core-image-sato image, about more 15 seconds are needed
> 
>   + Disk space usage:
>     - Nearly no changes:
>     $ ls -lh BEFORE.rootfs.ext3 AFTER.rootfs.ext3 | awk '{print $5"\t"$NF}'
>     357M BEFORE.rootfs.ext3
>     357M AFTER.rootfs.ext3
>     
>     $ du -sh BEFORE.rootfs.ext3 AFTER.rootfs.ext3
>     238M    BEFORE.rootfs.ext3
>     357M    AFTER.rootfs.ext3
>     # This is different because BEFORE.rootfs.ext3 has sparse files,
>     # they are very similar (less than 1M gap) after mount them and run
>     # "du -sh".

I can live with the performance issues however as I understand this
code, its breaking both sparse files and also likely hardlinked files.
I'm not sure we have many sparse ones but we do have packages with heavy
hardlinking (the sdk image toolchain packages for example).

Adding the script to e2fsprogs isn't a problem but I am tempted to wait
until this work is completed before we start using it instead of
genext2fs.

Cheers,

Richard
Darren Hart - March 3, 2013, 5:15 p.m.
On 03/02/2013 03:39 AM, Richard Purdie wrote:
> On Sat, 2013-03-02 at 18:46 +0800, Robert Yang wrote:
>> Replace genext2fs with populate-extfs.sh in image_types.bbclass to fully
>> support ext3/ext4 rootfs.
>>
>> Comments from Darren:
>> We used genext2fs to create ext3/ext4 rootfs in the past, basically,
>> genext2fs doesn't support creating ext4 filesystems. It creates, as I
>> understand it, an ext2 filesystem, then adds a journal, and sets some
>> bits. It can't support the newer features like extents. So what we end
>> up with is a bit of a hack for a filesystem.
>>
>> The ext tools (e2fsprogs) unfortunately don't provide an integrated
>> solution for generating prepopulated filesystem images as many other
>> mkfs* tools do. One thing missing was symlink support in libext2fs. I
>> added that support and demonstrated a script which uses the e2fsprogs
>> debugfs tool that can populate the newly formatted filesystem from a
>> directory and without root privileges.
>>
>> This patches integrate this stage of development into OE-Core. We can
>> go about this in two ways. One is to just prototype this in a branch and
>> use it to validate the functionality and not make any changes to oe-core
>> image generation until mke2fs has initial directory support. The other
>> is to merge this and get broader testing of the concept and later move
>> to the full mke2fs implementation once it becomes available. I
>> understand the resistance to the latter, but long term I think it will
>> result in a more robust solution as we will have caught more of the
>> corner cases and have been able to do a better job integrating into
>> mke2fs the first time.
>>
>>
>> * Impact:
>>   + Rootfs generation time:
>>     - For a core-image-minimal image, about more 3 seconds are needed
>>     - For a core-image-sato image, about more 15 seconds are needed
>>
>>   + Disk space usage:
>>     - Nearly no changes:
>>     $ ls -lh BEFORE.rootfs.ext3 AFTER.rootfs.ext3 | awk '{print $5"\t"$NF}'
>>     357M BEFORE.rootfs.ext3
>>     357M AFTER.rootfs.ext3
>>     
>>     $ du -sh BEFORE.rootfs.ext3 AFTER.rootfs.ext3
>>     238M    BEFORE.rootfs.ext3
>>     357M    AFTER.rootfs.ext3
>>     # This is different because BEFORE.rootfs.ext3 has sparse files,
>>     # they are very similar (less than 1M gap) after mount them and run
>>     # "du -sh".
> 
> I can live with the performance issues however as I understand this
> code, its breaking both sparse files and also likely hardlinked files.
> I'm not sure we have many sparse ones but we do have packages with heavy
> hardlinking (the sdk image toolchain packages for example).
> 
> Adding the script to e2fsprogs isn't a problem but I am tempted to wait
> until this work is completed before we start using it instead of
> genext2fs.


Agreed, I thought we were within 1MB on size from my reading of the
previous discussion. Robert, do you have any thoughts on what is needed
to address the hardlinks? That seems like something we should be able to
address quickly.

Same question for the sparse files, although I could see that taking
some additional effort.
Darren Hart - March 3, 2013, 6:21 p.m.
On 03/03/2013 09:15 AM, Darren Hart wrote:
> 
> 
> On 03/02/2013 03:39 AM, Richard Purdie wrote:
>> On Sat, 2013-03-02 at 18:46 +0800, Robert Yang wrote:
>>> Replace genext2fs with populate-extfs.sh in image_types.bbclass to fully
>>> support ext3/ext4 rootfs.
>>>
>>> Comments from Darren:
>>> We used genext2fs to create ext3/ext4 rootfs in the past, basically,
>>> genext2fs doesn't support creating ext4 filesystems. It creates, as I
>>> understand it, an ext2 filesystem, then adds a journal, and sets some
>>> bits. It can't support the newer features like extents. So what we end
>>> up with is a bit of a hack for a filesystem.
>>>
>>> The ext tools (e2fsprogs) unfortunately don't provide an integrated
>>> solution for generating prepopulated filesystem images as many other
>>> mkfs* tools do. One thing missing was symlink support in libext2fs. I
>>> added that support and demonstrated a script which uses the e2fsprogs
>>> debugfs tool that can populate the newly formatted filesystem from a
>>> directory and without root privileges.
>>>
>>> This patches integrate this stage of development into OE-Core. We can
>>> go about this in two ways. One is to just prototype this in a branch and
>>> use it to validate the functionality and not make any changes to oe-core
>>> image generation until mke2fs has initial directory support. The other
>>> is to merge this and get broader testing of the concept and later move
>>> to the full mke2fs implementation once it becomes available. I
>>> understand the resistance to the latter, but long term I think it will
>>> result in a more robust solution as we will have caught more of the
>>> corner cases and have been able to do a better job integrating into
>>> mke2fs the first time.
>>>
>>>
>>> * Impact:
>>>   + Rootfs generation time:
>>>     - For a core-image-minimal image, about more 3 seconds are needed
>>>     - For a core-image-sato image, about more 15 seconds are needed
>>>
>>>   + Disk space usage:
>>>     - Nearly no changes:
>>>     $ ls -lh BEFORE.rootfs.ext3 AFTER.rootfs.ext3 | awk '{print $5"\t"$NF}'
>>>     357M BEFORE.rootfs.ext3
>>>     357M AFTER.rootfs.ext3
>>>     
>>>     $ du -sh BEFORE.rootfs.ext3 AFTER.rootfs.ext3
>>>     238M    BEFORE.rootfs.ext3
>>>     357M    AFTER.rootfs.ext3
>>>     # This is different because BEFORE.rootfs.ext3 has sparse files,
>>>     # they are very similar (less than 1M gap) after mount them and run
>>>     # "du -sh".
>>
>> I can live with the performance issues however as I understand this
>> code, its breaking both sparse files and also likely hardlinked files.
>> I'm not sure we have many sparse ones but we do have packages with heavy
>> hardlinking (the sdk image toolchain packages for example).
>>
>> Adding the script to e2fsprogs isn't a problem but I am tempted to wait
>> until this work is completed before we start using it instead of
>> genext2fs.
> 
> 
> Agreed, I thought we were within 1MB on size from my reading of the
> previous discussion. Robert, do you have any thoughts on what is needed
> to address the hardlinks? That seems like something we should be able to
> address quickly.
> 
> Same question for the sparse files, although I could see that taking
> some additional effort.

By the way, this is exactly the kind of thing we were hoping to catch by
using the debugfs as an intermediate step. If anything needs to be added
to libext2fs, we want to know before we jump into the mke2fs solution.
So this is working as planned - just maybe sooner than expected, which
is great.
Robert Yang - March 4, 2013, 1:42 p.m.
On 03/04/2013 02:21 AM, Darren Hart wrote:
>
>
> On 03/03/2013 09:15 AM, Darren Hart wrote:
>>
>>
>> On 03/02/2013 03:39 AM, Richard Purdie wrote:
>>> On Sat, 2013-03-02 at 18:46 +0800, Robert Yang wrote:
>>>> Replace genext2fs with populate-extfs.sh in image_types.bbclass to fully
>>>> support ext3/ext4 rootfs.
>>>>
>>>> Comments from Darren:
>>>> We used genext2fs to create ext3/ext4 rootfs in the past, basically,
>>>> genext2fs doesn't support creating ext4 filesystems. It creates, as I
>>>> understand it, an ext2 filesystem, then adds a journal, and sets some
>>>> bits. It can't support the newer features like extents. So what we end
>>>> up with is a bit of a hack for a filesystem.
>>>>
>>>> The ext tools (e2fsprogs) unfortunately don't provide an integrated
>>>> solution for generating prepopulated filesystem images as many other
>>>> mkfs* tools do. One thing missing was symlink support in libext2fs. I
>>>> added that support and demonstrated a script which uses the e2fsprogs
>>>> debugfs tool that can populate the newly formatted filesystem from a
>>>> directory and without root privileges.
>>>>
>>>> This patches integrate this stage of development into OE-Core. We can
>>>> go about this in two ways. One is to just prototype this in a branch and
>>>> use it to validate the functionality and not make any changes to oe-core
>>>> image generation until mke2fs has initial directory support. The other
>>>> is to merge this and get broader testing of the concept and later move
>>>> to the full mke2fs implementation once it becomes available. I
>>>> understand the resistance to the latter, but long term I think it will
>>>> result in a more robust solution as we will have caught more of the
>>>> corner cases and have been able to do a better job integrating into
>>>> mke2fs the first time.
>>>>
>>>>
>>>> * Impact:
>>>>    + Rootfs generation time:
>>>>      - For a core-image-minimal image, about more 3 seconds are needed
>>>>      - For a core-image-sato image, about more 15 seconds are needed
>>>>
>>>>    + Disk space usage:
>>>>      - Nearly no changes:
>>>>      $ ls -lh BEFORE.rootfs.ext3 AFTER.rootfs.ext3 | awk '{print $5"\t"$NF}'
>>>>      357M BEFORE.rootfs.ext3
>>>>      357M AFTER.rootfs.ext3
>>>>
>>>>      $ du -sh BEFORE.rootfs.ext3 AFTER.rootfs.ext3
>>>>      238M    BEFORE.rootfs.ext3
>>>>      357M    AFTER.rootfs.ext3
>>>>      # This is different because BEFORE.rootfs.ext3 has sparse files,
>>>>      # they are very similar (less than 1M gap) after mount them and run
>>>>      # "du -sh".
>>>
>>> I can live with the performance issues however as I understand this
>>> code, its breaking both sparse files and also likely hardlinked files.
>>> I'm not sure we have many sparse ones but we do have packages with heavy
>>> hardlinking (the sdk image toolchain packages for example).
>>>
>>> Adding the script to e2fsprogs isn't a problem but I am tempted to wait
>>> until this work is completed before we start using it instead of
>>> genext2fs.
>>
>>
>> Agreed, I thought we were within 1MB on size from my reading of the
>> previous discussion. Robert, do you have any thoughts on what is needed
>> to address the hardlinks? That seems like something we should be able to

Yes, we do have hard links in the rootfs, e.g: core-image-sato and 
core-image-sato-sdk:

# The sato
$ find core-image-sato/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v '1$'
core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt200 26977609 2
core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt220 26977609 2
core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26978690 2
core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26978690 2

# The sato-sdk:
$ find core-image-sato-sdk/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v 
'1$'
core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt200 26903519 2
core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt220 26903519 2
core-image-sato-sdk/1.0-r0/rootfs/usr/include/et/com_err.h 28058656 2
core-image-sato-sdk/1.0-r0/rootfs/usr/include/com_err.h 28058656 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26900939 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlbug 26899680 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk-4.0.1 26900368 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/psed 26899667 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/s2p 26899667 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/c2ph 26899695 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlthanks 26899680 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/pstruct 26899695 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26900939 2
core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk 26900368 2

We can make hard links according to these information, and the find command is
very fast, so it would not cost much time.


>> address quickly.
>>
>> Same question for the sparse files, although I could see that taking
>> some additional effort.
>

I don't find any obvious sparse files by the following command:

# sato:
$ find core-image-sato/1.0-r0/rootfs/ -size +8 -printf "%p #%S\n" | grep -v 
'#0\|#1' | wc -l
0

# sato-sdk:
$ find core-image-sato-sdk/1.0-r0/rootfs/ -size +8 -printf "%p #%S\n" | grep -v 
'#0\|#1' | wc -l
0

I will send an official patch for review with the hard links solution if you
are fine with it.

// Robert


> By the way, this is exactly the kind of thing we were hoping to catch by
> using the debugfs as an intermediate step. If anything needs to be added
> to libext2fs, we want to know before we jump into the mke2fs solution.
> So this is working as planned - just maybe sooner than expected, which
> is great.
>
Robert Yang - March 4, 2013, 2:09 p.m.
On 03/04/2013 09:42 PM, Robert Yang wrote:
>
>
> On 03/04/2013 02:21 AM, Darren Hart wrote:
>>
>>
>> On 03/03/2013 09:15 AM, Darren Hart wrote:
>>>
>>>
>>> On 03/02/2013 03:39 AM, Richard Purdie wrote:
>>>> On Sat, 2013-03-02 at 18:46 +0800, Robert Yang wrote:
>>>>> Replace genext2fs with populate-extfs.sh in image_types.bbclass to fully
>>>>> support ext3/ext4 rootfs.
>>>>>
>>>>> Comments from Darren:
>>>>> We used genext2fs to create ext3/ext4 rootfs in the past, basically,
>>>>> genext2fs doesn't support creating ext4 filesystems. It creates, as I
>>>>> understand it, an ext2 filesystem, then adds a journal, and sets some
>>>>> bits. It can't support the newer features like extents. So what we end
>>>>> up with is a bit of a hack for a filesystem.
>>>>>
>>>>> The ext tools (e2fsprogs) unfortunately don't provide an integrated
>>>>> solution for generating prepopulated filesystem images as many other
>>>>> mkfs* tools do. One thing missing was symlink support in libext2fs. I
>>>>> added that support and demonstrated a script which uses the e2fsprogs
>>>>> debugfs tool that can populate the newly formatted filesystem from a
>>>>> directory and without root privileges.
>>>>>
>>>>> This patches integrate this stage of development into OE-Core. We can
>>>>> go about this in two ways. One is to just prototype this in a branch and
>>>>> use it to validate the functionality and not make any changes to oe-core
>>>>> image generation until mke2fs has initial directory support. The other
>>>>> is to merge this and get broader testing of the concept and later move
>>>>> to the full mke2fs implementation once it becomes available. I
>>>>> understand the resistance to the latter, but long term I think it will
>>>>> result in a more robust solution as we will have caught more of the
>>>>> corner cases and have been able to do a better job integrating into
>>>>> mke2fs the first time.
>>>>>
>>>>>
>>>>> * Impact:
>>>>>    + Rootfs generation time:
>>>>>      - For a core-image-minimal image, about more 3 seconds are needed
>>>>>      - For a core-image-sato image, about more 15 seconds are needed
>>>>>
>>>>>    + Disk space usage:
>>>>>      - Nearly no changes:
>>>>>      $ ls -lh BEFORE.rootfs.ext3 AFTER.rootfs.ext3 | awk '{print $5"\t"$NF}'
>>>>>      357M BEFORE.rootfs.ext3
>>>>>      357M AFTER.rootfs.ext3
>>>>>
>>>>>      $ du -sh BEFORE.rootfs.ext3 AFTER.rootfs.ext3
>>>>>      238M    BEFORE.rootfs.ext3
>>>>>      357M    AFTER.rootfs.ext3
>>>>>      # This is different because BEFORE.rootfs.ext3 has sparse files,
>>>>>      # they are very similar (less than 1M gap) after mount them and run
>>>>>      # "du -sh".
>>>>
>>>> I can live with the performance issues however as I understand this
>>>> code, its breaking both sparse files and also likely hardlinked files.
>>>> I'm not sure we have many sparse ones but we do have packages with heavy
>>>> hardlinking (the sdk image toolchain packages for example).
>>>>
>>>> Adding the script to e2fsprogs isn't a problem but I am tempted to wait
>>>> until this work is completed before we start using it instead of
>>>> genext2fs.
>>>
>>>
>>> Agreed, I thought we were within 1MB on size from my reading of the
>>> previous discussion. Robert, do you have any thoughts on what is needed
>>> to address the hardlinks? That seems like something we should be able to
>
> Yes, we do have hard links in the rootfs, e.g: core-image-sato and
> core-image-sato-sdk:
>
> # The sato
> $ find core-image-sato/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v '1$'
> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt200 26977609 2
> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt220 26977609 2
> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26978690 2
> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26978690 2
>
> # The sato-sdk:
> $ find core-image-sato-sdk/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v
> '1$'
> core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt200 26903519 2
> core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt220 26903519 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/include/et/com_err.h 28058656 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/include/com_err.h 28058656 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26900939 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlbug 26899680 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk-4.0.1 26900368 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/psed 26899667 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/s2p 26899667 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/c2ph 26899695 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlthanks 26899680 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/pstruct 26899695 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26900939 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk 26900368 2
>
> We can make hard links according to these information, and the find command is
> very fast, so it would not cost much time.
>
>
>>> address quickly.
>>>
>>> Same question for the sparse files, although I could see that taking
>>> some additional effort.
>>
>
> I don't find any obvious sparse files by the following command:
>

Sorry, we do have several sparse files, the command was wrong, it should be:

# sato:

$ find core-image-sato/1.0-r0/rootfs/ -size +8 -printf "%p #%S\n" | grep -v '#1'
core-image-sato/1.0-r0/rootfs/var/lib/rpm/Sha1header #0.916667
core-image-sato/1.0-r0/rootfs/var/lib/rpm/log/log.0000000001 #0.837109
core-image-sato/1.0-r0/rootfs/var/lib/rpm/Filedigests #0.857143

3 files

# sato-sdk:
$ find core-image-sato-sdk/1.0-r0/rootfs/ -size +8 -printf "%p #%S\n" | grep -v '#1'
core-image-sato-sdk/1.0-r0/rootfs/var/lib/rpm/Sigmd5 #0.904762
core-image-sato-sdk/1.0-r0/rootfs/var/lib/rpm/Sha1header #0.857143
core-image-sato-sdk/1.0-r0/rootfs/var/lib/rpm/log/log.0000000007 #0.150781
core-image-sato-sdk/1.0-r0/rootfs/var/lib/rpm/Filedigests #0.847619

4 files

I don't have any good ideas on how to fix the sparse files currently, it seems
that we should modify the debugfs' "write" command to let it can create the
sparse files, just like cp's --sparse=WHEN.

// Robert

> # sato:
> $ find core-image-sato/1.0-r0/rootfs/ -size +8 -printf "%p #%S\n" | grep -v
> '#0\|#1' | wc -l
> 0
>
> # sato-sdk:
> $ find core-image-sato-sdk/1.0-r0/rootfs/ -size +8 -printf "%p #%S\n" | grep -v
> '#0\|#1' | wc -l
> 0
>
> I will send an official patch for review with the hard links solution if you
> are fine with it.
>
> // Robert
>
>
>> By the way, this is exactly the kind of thing we were hoping to catch by
>> using the debugfs as an intermediate step. If anything needs to be added
>> to libext2fs, we want to know before we jump into the mke2fs solution.
>> So this is working as planned - just maybe sooner than expected, which
>> is great.
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Richard Purdie - March 4, 2013, 2:10 p.m.
On Mon, 2013-03-04 at 21:42 +0800, Robert Yang wrote:
> 
> On 03/04/2013 02:21 AM, Darren Hart wrote:
> >
> >
> > On 03/03/2013 09:15 AM, Darren Hart wrote:

> Yes, we do have hard links in the rootfs, e.g: core-image-sato and 
> core-image-sato-sdk:
> 
> # The sato
> $ find core-image-sato/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v '1$'
> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt200 26977609 2
> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt220 26977609 2
> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26978690 2
> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26978690 2

What if the count was 11? or 21? I'm just mentioning we need to improve
that command!

> # The sato-sdk:
> $ find core-image-sato-sdk/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v 
> '1$'
> core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt200 26903519 2
> core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt220 26903519 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/include/et/com_err.h 28058656 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/include/com_err.h 28058656 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26900939 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlbug 26899680 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk-4.0.1 26900368 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/psed 26899667 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/s2p 26899667 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/c2ph 26899695 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlthanks 26899680 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/pstruct 26899695 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26900939 2
> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk 26900368 2

I'm slightly surprised there aren't more hardlinks for gcc in here. A
meta-toolchain-sdk tarball will probably have a load of hardlinks in too
if you want something to test with (we don't usually make extX images
for the toolchain though).

Cheers,

Richard
Darren Hart - March 4, 2013, 4:09 p.m.
On 03/04/2013 06:10 AM, Richard Purdie wrote:
> On Mon, 2013-03-04 at 21:42 +0800, Robert Yang wrote:
>>
>> On 03/04/2013 02:21 AM, Darren Hart wrote:
>>>
>>>
>>> On 03/03/2013 09:15 AM, Darren Hart wrote:
> 
>> Yes, we do have hard links in the rootfs, e.g: core-image-sato and 
>> core-image-sato-sdk:
>>
>> # The sato
>> $ find core-image-sato/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v '1$'
>> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt200 26977609 2
>> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt220 26977609 2
>> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26978690 2
>> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26978690 2
> 
> What if the count was 11? or 21? I'm just mentioning we need to improve
> that command!

Yes a -v ' 1$' would be better.
Robert Yang - March 5, 2013, 8:24 a.m.
On 03/04/2013 10:10 PM, Richard Purdie wrote:
> On Mon, 2013-03-04 at 21:42 +0800, Robert Yang wrote:
>>
>> On 03/04/2013 02:21 AM, Darren Hart wrote:
>>>
>>>
>>> On 03/03/2013 09:15 AM, Darren Hart wrote:
>
>> Yes, we do have hard links in the rootfs, e.g: core-image-sato and
>> core-image-sato-sdk:
>>
>> # The sato
>> $ find core-image-sato/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v '1$'
>> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt200 26977609 2
>> core-image-sato/1.0-r0/rootfs/etc/terminfo/v/vt220 26977609 2
>> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26978690 2
>> core-image-sato/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26978690 2
>
> What if the count was 11? or 21? I'm just mentioning we need to improve
> that command!
>
>> # The sato-sdk:
>> $ find core-image-sato-sdk/1.0-r0/rootfs/ -type f -printf "%p %i %n\n" | grep -v
>> '1$'
>> core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt200 26903519 2
>> core-image-sato-sdk/1.0-r0/rootfs/etc/terminfo/v/vt220 26903519 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/include/et/com_err.h 28058656 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/include/com_err.h 28058656 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld.bfd 26900939 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlbug 26899680 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk-4.0.1 26900368 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/psed 26899667 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/s2p 26899667 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/c2ph 26899695 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/perlthanks 26899680 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/pstruct 26899695 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/arm-poky-linux-gnueabi-ld 26900939 2
>> core-image-sato-sdk/1.0-r0/rootfs/usr/bin/gawk 26900368 2
>
> I'm slightly surprised there aren't more hardlinks for gcc in here. A
> meta-toolchain-sdk tarball will probably have a load of hardlinks in too
> if you want something to test with (we don't usually make extX images
> for the toolchain though).
>

The hardlinks result from the meta-toolchain-sdk is similar:

$ find sdk/image/opt/poky/1.3+snapshot/sysroots/ -type f -printf "%p %i %n\n" | 
grep -v ' 1$'
sdk/image/opt/poky/1.3+snapshot/sysroots/armv5te-poky-linux-gnueabi/etc/terminfo/v/vt200 
27337495 2
sdk/image/opt/poky/1.3+snapshot/sysroots/armv5te-poky-linux-gnueabi/etc/terminfo/v/vt220 
27337495 2
sdk/image/opt/poky/1.3+snapshot/sysroots/armv5te-poky-linux-gnueabi/usr/include/et/com_err.h 
27468703 2
sdk/image/opt/poky/1.3+snapshot/sysroots/armv5te-poky-linux-gnueabi/usr/include/com_err.h 
27468703 2
sdk/image/opt/poky/1.3+snapshot/sysroots/armv5te-poky-linux-gnueabi/usr/bin/gawk-4.0.1 
27297079 2
sdk/image/opt/poky/1.3+snapshot/sysroots/armv5te-poky-linux-gnueabi/usr/bin/gawk 
27297079 2
sdk/image/opt/poky/1.3+snapshot/sysroots/x86_64-pokysdk-linux/etc/terminfo/v/vt200 
27469810 2
sdk/image/opt/poky/1.3+snapshot/sysroots/x86_64-pokysdk-linux/etc/terminfo/v/vt220 
27469810 2
sdk/image/opt/poky/1.3+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-ld.bfd 
27484702 2
sdk/image/opt/poky/1.3+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-ld 
27484702 2

I wonder what's next step please, can we ignore the sparse files at the moment,
and then I will send an patch for review with the hardlink fixes.

// Robert

> Cheers,
>
> Richard
>
>
>