Hello Jordi, Jordi Pujol <jordipujolp@xxxxxxxxx> writes: > that is a list of some errors found when doiing a remaster that uses > overlayfs as a filesystem modification layer, Thanks for testing. > After doing a big package upgrade we note that the rootdir has some errors, > this is only a little percent of the total files contained in the filesystem, > 44 files of 86173 > > overlayfs mounted on /tmp/live-net-remaster-pro1Wm/chroot type overlayfs > options rw,relatime,lowerdir=/tmp/live-net-remaster- > pro1Wm/image/00filesystem.squashfs,upperdir=/home/tmp.7P8ARuGANF > > CASE 1: complete directory /usr/share/doc/xorg disappears, > is in lowerdir, has not been modified, but rootdir does not show it, I see the common theme in all these cases: a file should be there in rootdir but isn't. I also see that you are using 'find'. Does the file show if you are using 'ls'? ls /tmp/live-net-remaster-pro1Wm/chroot/usr/share/doc/ | grep xorg ls -d /tmp/live-net-remaster-pro1Wm/chroot/usr/share/doc/xorg Could you please do a strace of 'find' strace -v -o /tmp/strace find /tmp/live-net-remaster-pro1Wm/chroot/usr/share/doc/ -maxdepth 1 -name 'xorg*' And send the resulting trace in /tmp/strace? Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html