linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: David Michael <fedora.dm0@gmail.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: Compatibility with overlayfs
Date: Sat, 30 Nov 2019 09:29:04 +0800	[thread overview]
Message-ID: <20191130012900.GA2862@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <CAEvUa7nxnby+rxK-KRMA46=exeOMApkDMAV08AjMkkPnTPV4CQ@mail.gmail.com>

Hi David,

On Fri, Nov 29, 2019 at 03:22:15PM -0500, David Michael wrote:
> Hi,
> 
> I tried to test EROFS on Linux 5.4 as the root file system and mounted
> a writable overlay (with upper layer on tmpfs) over /etc, but I get
> ENODATA errors when attempting to modify files.  For example, adding a
> user results in "Failed to take /etc/passwd lock: No data available".
> Files can be modified after unlinking and restoring them so they're
> created on the upper layer.  This is not necessary with other
> read-only file systems (at least squashfs or ext4 with the read-only
> feature).  I tried while forcing compact and extended inodes.
> 
> Is EROFS intended to be usable as a lower layer with overlayfs?

Yes, and overlayfs were used on our smartphones for development use
only as well. I think it's weird, I will try it on the latest kernel
now, and see if I can reproduce this issue soon...

Thanks for your report!

Thanks,
Gao Xiang

> 
> Thanks.
> 
> David

  reply	other threads:[~2019-11-30  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 20:22 Compatibility with overlayfs David Michael
2019-11-30  1:29 ` Gao Xiang via Linux-erofs [this message]
2019-11-30  2:13   ` Gao Xiang via Linux-erofs
2019-11-30 15:15     ` David Michael
2019-11-30 16:27       ` Gao Xiang via Linux-erofs

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=20191130012900.GA2862@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=linux-erofs@lists.ozlabs.org \
    --cc=fedora.dm0@gmail.com \
    --cc=hsiangkao@aol.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;
as well as URLs for NNTP newsgroup(s).