[OE-core] [PATCH] populate_sdk_base: repeat to tar archive file five time

Otavio Salvador otavio at ossystems.com.br
Thu Oct 17 11:58:50 UTC 2013


On Wed, Oct 16, 2013 at 11:01 PM, Rongqing Li <rongqing.li at windriver.com> wrote:
> On 10/16/2013 08:12 PM, Richard Purdie wrote:
>>
>> On Wed, 2013-10-16 at 14:34 +0800, Rongqing Li wrote:
>>>
>>>
>>> On 10/16/2013 02:24 PM, Otavio Salvador wrote:
>>>>
>>>> On Wed, Oct 16, 2013 at 2:53 AM,  <rongqing.li at windriver.com> wrote:
>>>>>
>>>>> From: Roy Li <rongqing.li at windriver.com>
>>>>>
>>>>> [YOCTO #5287]
>>>>>
>>>>> tar failed and reported that file changed as we read it, now
>>>>> we workaround it
>>>>>
>>>>> Signed-off-by: Roy Li <rongqing.li at windriver.com>
>>>>
>>>>
>>>> You must be kidding right?! loop 5 times?!? why not fix the root cause
>>>> of the change?
>>>>
>>>
>>> Sorry, I do not know the root cause, and I see many people spent
>>> lots of efforts to investigate, but do not find the root cause,
>>> sometime we suspect it is the building servers kernel issue,
>>> if it is true, we can not fix the building servers, we only
>>> workaround the code.
>>
>>
>> This workaround is not going into master, its horrid. Do we know which
>> versions of the kernel on the server have the issue. I'd much rather
>> tell people to fix their broken filesystems for example and refuse to
>> run on them.
>>
>
> I saw it happened on CentOS 5.9 and RedHat 5.5, and We deployed lots
> of them, it is hard to replace them.
>
> The bug did not happen everytime, only intermittently, this workaround
> is ugly, but it is better than fixing the servers, or declaring them
> as unsupported server.

This workaround may make it hard to happen but it is not a fix and
nothing guarantee it is enough for all cases; so I think forcing tar
to rerun for all machine because of two broken distributions is not an
option. We need to find other way to fix this.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750



More information about the Openembedded-core mailing list