[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    Re: [OE-core] [PATCH] Use shutil.move when os.rename fails
From:       "Devendra Tewari" <devendra.tewari () gmail ! com>
Date:       2021-04-28 23:02:32
Message-ID: 74CCF8C8-CE6E-43AA-95F8-F38FB64B656B () gmail ! com
[Download RAW message or body]

Understood - carrying patches is a burden for sure. I'll maintain patches for my own \
narrow use cases at my end, and perhaps submit them upstream.

Thanks,
Devendra

> On 28 Apr 2021, at 18:42, Richard Purdie <richard.purdie@linuxfoundation.org> \
> wrote: 
> On Wed, 2021-04-28 at 07:00 -0300, Devendra Tewari wrote:
> > The gist of it is that Docker uses the overlay2 storage driver by default, 
> > previously it used aufs. Both drivers have the same limitation in rename, 
> > where file rename across layers is handled by moving, but directory rename
> > across layers results in error EXDEV. It is up to user space to handle the error.
> 
> I'm still struggling to see how you're going to patch all the various pieces of
> software out there used during a build to handle EXDEV correctly.
> 
> We have handled some cases of this for a long time where we're moving files
> over to different parts of a filesystem, e.g. /tmp/ to WORKDIR or vice versa.
> 
> This new docker case triggers for renames even within a directory, e.g. 
> /some/path/a -> /some/path/b which is not something that would often trigger
> this.
> 
> I need to say clearly now that we are not carrying/taking patches to patch
> every bit of other software to try and avoid this.
> 
> Cheers,
> 
> Richard
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#151070): https://lists.openembedded.org/g/openembedded-core/message/151070
Mute This Topic: https://lists.openembedded.org/mt/81698791/4454766
Group Owner: openembedded-core+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [openembedded-core@marc.info]
-=-=-=-=-=-=-=-=-=-=-=-



[prev in list] [next in list] [prev in thread] [next in thread]