All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Klaus A. Kreil" <klaus.kreil@univie.ac.at>
To: linux-kernel@vger.kernel.org
Subject: unable to mount using overlayfs.v22 on kernel 3.15.5
Date: Tue, 22 Jul 2014 23:40:05 +0200	[thread overview]
Message-ID: <53CEDA35.40301@univie.ac.at> (raw)

Hello list,
I have just found out about this mailing list which obviously also takes 
care of overlayfs.

I have been a happy user of overlayfs for quiet some time using it to 
propagate a shared r/o LVM ext4 lowerdir rootfs with a small r/w ext4 
upperdir for a number of XEN domU guests. I started with overlayfs on 
kernel version 3.11.7 (all on gentoo-hardened). Recently I have switched 
from 3.13.10 (using overlayfs.v21) to 3.15.5 with overlayfs.v22.

overlayfs.v22 seems to have changed insofar as there's a new parameter 
workdir=/dir with dir required to be an empty directory on the same 
filesystem as upperdir. So I have changed my initramfs to include that 
parameter and have also created my /dir directory (named /.work, owned 
by root:root and 0755 mode) on all my individual upperdir filesystems 
for all of my XEN domUs.

Now when I start the new kernel 3.15.5 with the modified init script 
from the newly created initramfs, I am ending up in a rescue shell. Both 
the upper and lower filesystem are (as expected) mounted appropriately 
to /mnt/root_ro and /mnt/root_rw amd /mnt/root exists. Howeverm, trying 
to combine those two filesystems on /mnt/root (as before and regardless 
of whether used with or without the workdir= parameter) fails with an 
error message as follows:

# mount -t overlayfs overlayfs -o 
lowerdir=/mnt/root_ro,upperdir=/mnt/root_rw,workdir=/.work /mnt/root
mount: mounting overlayfs on /mnt/root failed: Invalid argument

The error message stays the same regardless of where on the command line 
the overlayfs "device" parameter appears. I can't see what's wrong with 
the command line given that - with the exception of the workdir=/.work 
part - the command has not changed from 3.13.10 (overlayfs.v21), 
therefore currently leaving me at loss.

I would very much appreciate any help and support in tracking down this 
unexpected issue.

Regards Atom2

             reply	other threads:[~2014-07-22 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 21:40 Klaus A. Kreil [this message]
2014-07-24 12:14 ` unable to mount using overlayfs.v22 on kernel 3.15.5 Woody Suwalski
2014-07-24 13:48   ` Klaus A. Kreil

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=53CEDA35.40301@univie.ac.at \
    --to=klaus.kreil@univie.ac.at \
    --cc=linux-kernel@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.