From: Jordi Pujol <jordipujolp@gmail.com>
To: linux-fsdevel@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>
Subject: overlayfs v8 problems with whiteout links
Date: Fri, 22 Apr 2011 10:43:43 +0200 [thread overview]
Message-ID: <201104221043.43380.jordipujolp@gmail.com> (raw)
Hello,
Now working on a persistent Live that uses overlayfs v8 and
tmpfs xattrs, all works near well but sometimes whiteout fails,
I think maybe xattrs create and delete is not synchronized with the operations
create and delete for whiteout links.
these are commands from a Debian package build,
showing a command "rm -rf" that cannot remove the files because a whiteout link
was not removed successfully.
dpkg-deb: building package `nvidia-kernel-2.6.38-4.jpp.1-lnet-amd64' in
`/usr/src/nvidia-kernel-2.6.38-4.jpp.1-lnet-
amd64_270.41.06-1.lnet1+2.6.38-16_amd64.deb'.
dh_prep
rm: cannot remove `debian/nvidia-kernel-2.6.38-4.jpp.1-lnet-amd64/DEBIAN':
Directory not empty
dh_prep: rm -rf debian/nvidia-kernel-2.6.38-4.jpp.1-lnet-amd64/ returned exit
code 1
the directory listing shows the whiteout, but it must be hidden,
# ls -R1l nvidia-kernel-2.6.38-4.jpp.1-lnet-amd64
nvidia-kernel-2.6.38-4.jpp.1-lnet-amd64:
total 4
drwxr-xr-x 2 root root 4096 2011-04-22 10:19 DEBIAN
nvidia-kernel-2.6.38-4.jpp.1-lnet-amd64/DEBIAN:
total 0
lrwxrwxrwx 1 root root 18 2011-04-22 10:19 control -> (overlay-whiteout)
Thanks,
Jordi Pujol
Live never ending Tale
GNU/Linux Live forever!
http://livenet.selfip.com
next reply other threads:[~2011-04-22 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 8:43 Jordi Pujol [this message]
2011-04-23 12:43 ` overlayfs v8 problems with whiteout links Jordi Pujol
2011-04-23 14:51 ` Jordi Pujol
2011-04-24 18:08 ` Jordi Pujol
2011-04-26 15:50 ` Miklos Szeredi
2011-04-27 7:57 ` Jordi Pujol
2011-04-27 11:41 ` Miklos Szeredi
2011-04-27 13:30 ` Jordi Pujol
2011-04-27 14:50 ` Jordi Pujol
2011-04-27 18:52 ` Miklos Szeredi
2011-04-26 15:34 ` Miklos Szeredi
2011-04-27 9:36 ` Jordi Pujol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201104221043.43380.jordipujolp@gmail.com \
--to=jordipujolp@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).