All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: overlayfs 4.19: unable to make backup link: Invalid cross-device link
Date: Sat, 27 Oct 2018 16:04:50 -0400	[thread overview]
Message-ID: <20181027200450.GA5909@thunk.org> (raw)

I was rebuilding my dropbox Docker container, and it failed in 4.19
with the following error:

dpkg: error processing archive /var/cache/apt/archives/perl-base_5.20.2-3+deb8u11_amd64.deb (--unpack):
 unable to make backup link of `./usr/bin/perl5.20.2' before installing new version: Invalid cross-device link
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
dpkg: error: error creating new backup file '/var/lib/dpkg/status-old': Invalid cross-device link
E: Sub-process /usr/bin/dpkg returned an error code (2)

When I booted the 4.18.0-2 kernel from Debian, the exact same Docker
file worked just fine.  With 4.19 it fails reliably.

To reproduce:

git clone https://github.com/tytso/docker-dropbox
cd docker-dropbox
docker build --no-cache .

I'm using a Debian testing (buster) userspace, using the docker-ce
from dropbox.com, version 18.03.1~ce-0~debian, using overlay2 storage
driverh.

Does this ring a bell at all?  Can someone give me some tips on how to
troubleshoot this?

Thanks!!

     	       	      	       	   - Ted

             reply	other threads:[~2018-10-28  4:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 20:04 Theodore Y. Ts'o [this message]
2018-10-29  7:37 ` overlayfs 4.19: unable to make backup link: Invalid cross-device link Amir Goldstein
2018-10-29  8:31 ` Miklos Szeredi
2018-10-29 22:04   ` Theodore Y. Ts'o
2018-10-30  4:44     ` Amir Goldstein
2018-11-14  9:46       ` Amir Goldstein
2018-11-14  9:55         ` Miklos Szeredi
2018-11-14 10:28           ` Maciej Zięba
2018-11-14 10:33             ` Maciej Zięba
2018-11-14 12:09             ` Amir Goldstein
2018-11-14 12:14               ` Maciej Zięba
2018-11-14 14:25               ` Vivek Goyal
2018-11-14 18:40                 ` Maciej Zięba
2018-11-14 21:33               ` Maciej Zięba

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=20181027200450.GA5909@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.