From: Sven Geggus <lists@fuchsschwanzdomain.de>
To: linux-kernel@vger.kernel.org
Subject: overlayfs (3.18-rc2): NFS completely unsupported?
Date: Thu, 30 Oct 2014 10:52:57 +0000 (UTC) [thread overview]
Message-ID: <m2t5a9$7fd$1@home.geggus.net> (raw)
Hello,
I'm testing overlayfs in kernel 3.18-rc2 because I hoped to be able to
replace aufs and would be able to return to mainline kernels in future.
overlayfs documentation states, that NFS is unsupported in "upper
filesystem", but I do not manage to make it work with a ro NFS lowerdir as
well. All I get is:
overlayfs: filesystem of lowerdir is not supported
This is what I try:
mount -t overlayfs -olowerdir=/etc,upperdir=/local/etc,workdir=/local/ovldir overlayfs /mnt
/local is tmpfs in this case.
If this is _not_ supposed to work I would strongly suggest, to clarify NFS
support in Documentation/filesystems/overlayfs.txt
Regards
Sven
--
"Das ist halt der Unterschied: Unix ist ein Betriebssystem mit Tradition,
die anderen sind einfach von sich aus unlogisch."
(Anselm Lingnau in de.comp.os.unix.discussion)
/me ist giggls@ircnet, http://sven.gegg.us/ im WWW
reply other threads:[~2014-10-30 11:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='m2t5a9$7fd$1@home.geggus.net' \
--to=lists@fuchsschwanzdomain.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox