From: Nikolay Borisov <kernel@kyup.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: SiteGround Operations <operations@siteground.com>,
linux-unionfs@vger.kernel.org
Subject: Problem writing to ovl with CIFS as lower dir
Date: Thu, 4 Feb 2016 18:02:42 +0200 [thread overview]
Message-ID: <56B37622.40604@kyup.com> (raw)
Hello,
[I'm not subscribed to the list please CC me when replying]
I'm testing overlayfs on 3.12 (own-made port) and on 4.4 (to confirm
behavior) and what I observe is that when I try to write to a file in
the merge directory e.g:
echo "test" > merged/test-file1
I get -EINVAL on 3.12 and -ENXIO on 4.4. However, when I try to touch a
file in the merged directory I have no issues. This happens only when
the lower mount is either CIFS/NFS. When it's another ext4 directory I
have no problems whatsoever. Is this behavior expected, I'm willing to
assume I've screwed up the 3.12 port but given that I see this on 4.4
(no custom modifications) I'm beginning to think this is innate into the
the design?
Regards,
Nikolay
next reply other threads:[~2016-02-04 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 16:02 Nikolay Borisov [this message]
2016-02-04 16:11 ` Problem writing to ovl with CIFS as lower dir David Howells
2016-02-04 17:28 ` Nikolay Borisov
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=56B37622.40604@kyup.com \
--to=kernel@kyup.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=operations@siteground.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox