All of lore.kernel.org
 help / color / mirror / Atom feed
From: radioconfusion@gmail.com
To: unlisted-recipients:; (no To-header on input)
Subject: Overlayfs regression: NFS as lowerdir fails to read any file
Date: Tue, 16 Feb 2016 12:41:42 -0800 (PST)	[thread overview]
Message-ID: <56c38986.cb97190a.e86bd.ffff9c12@mx.google.com> (raw)

Hello,

(I hope that is the right place to post. Posting to linux-unionfs was not allowed)
I think that I have found a regression/bug on overlayfs.
I can't get NFS lowerdir working with Linux 4.4 even though it's supported without custom patching. It worked with Linux 4.1 with little custom patching (see link below).

How to reproduce:
* Compile Linux 4.4 or any revision which is newer than "Commit 4bacc9 overlayfs: Make f_path always point to the overlay and f_inode to the underlay"
* Mount nfs with default options (my share is exported with (rw,sync,no_subtree_check))
* Mount overlay with nfs as lowerdir
* Try to read any existing file on overlayfs

Example:

# uname -r
4.3.0-1-amd64
# mkdir /tmp/nfs /tmp/upper /tmp/work /tmp/merge
# mount -o defaults 192.168.1.9:/home/shared /tmp/nfs
# mount -t overlay overlay -olowerdir=/tmp/nfs,upperdir=/tmp/upper,workdir=/tmp/work /tmp/merge
# mount | grep "/tmp"
192.168.1.9:/home/shared on /tmp/nfs type nfs4 (rw,relatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.15,local_lock=none,addr=192.168.1.9)
overlay on /tmp/merge type overlay (rw,relatime,lowerdir=/tmp/nfs,upperdir=/tmp/upper,workdir=/tmp/work)
# echo hello >/tmp/nfs/hello
# cat /tmp/merge/hello
cat: /tmp/merge/hello: No such device or address

I think my issue is same than:
http://www.spinics.net/lists/linux-unionfs/msg00386.html

NFS works as lowerdir without 4bacc9 (linux 4.1 for example) when nfs lowerdir is allowed by patching fs/overlayfs/super.c@692
See http://www.spinics.net/lists/linux-unionfs/msg00188.html for details.

Best Regards
Jussi

             reply	other threads:[~2016-02-16 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 20:41 radioconfusion [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-16 20:15 Overlayfs regression: NFS as lowerdir fails to read any file radioconfusion

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=56c38986.cb97190a.e86bd.ffff9c12@mx.google.com \
    --to=radioconfusion@gmail.com \
    /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.