linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: www <ouyangxuan10@163.com>
Cc: Kevin Locke <kevin@kevinlocke.name>,
	Miklos Szeredi <miklos@szeredi.hu>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	kernelnewbies@kernelnewbies.org
Subject: Re: [kernel]:overlayfs: invalid origin (root/bmcweb_persistent_data.json, ftype=8000, origin ftype=4000)
Date: Thu, 15 Apr 2021 20:09:23 +0300	[thread overview]
Message-ID: <CAOQ4uxgPq9E9xxwU2CDyHy-_yCZZeymg+3n+-6AqkGGE1YtwvQ@mail.gmail.com> (raw)
In-Reply-To: <6312af55.47e2.178d53227d0.Coremail.ouyangxuan10@163.com>

On Thu, Apr 15, 2021 at 2:03 PM www <ouyangxuan10@163.com> wrote:
>
> Dear Amir, kevin, miklos,
>
> An open source project uses overlay filesystem and systemd. when the system first time boot, there is an error in the file system:
> kernel: overlayfs: invalid origin (root/bmcweb_persistent_data.json, ftype=8000, origin ftype=4000)
>
> What's the reason for this? Can you give some help and suggestions to solve this problem?
>
> The details are as follows:
> 1. linux kernel version:
> root@N/A:~# uname -a Linux N/A 5.1.5-yocto-s-dirty-1605363 #1 Tue Apr 13 01:13:48 UTC 2021 armv6l GNU/Linux
>
> 2. mount command
> mount -t overlay -o lowerdir=$rodir,upperdir=$upper,workdir=$work cow /root
> (rodir=run/initramfs/ro, upper=run/initramfs/rw/cow, work=rwdir=run/initramfs/rw/work)
>
> 3. mountinfo
> root@N/A:~# cat /proc/self/mountinfo
> 13 21 0:6 / /dev rw,relatime shared:8 - devtmpfs dev rw,size=220800k,nr_inodes=55200,mode=755
> 14 21 0:13 / /sys rw,relatime shared:3 - sysfs sys rw
> 15 21 0:4 / /proc rw,relatime shared:2 - proc proc rw
> 16 21 0:14 / /run rw,nosuid,nodev shared:11 - tmpfs tmpfs rw,mode=755
> 17 16 7:0 / /run/initramfs/ro ro,relatime shared:12 - squashfs /dev/loop0 ro
> 18 16 31:5 / /run/initramfs/rw rw,relatime shared:13 - jffs2 /dev/mtdblock5 rw
> 21 0 0:15 / / rw,relatime shared:1 - overlay cow rw,lowerdir=run/initramfs/ro,upperdir=run/initramfs/rw/cow,workdir=run/initramfs/rw/work
> 22 13 0:17 / /dev/shm rw,nosuid,nodev shared:9 - tmpfs tmpfs rw
> 23 13 0:18 / /dev/pts rw,relatime shared:10 - devpts devpts rw,gid=5,mode=620,ptmxmode=000
> 24 14 0:19 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs ro,mode=755
> 25 24 0:20 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime shared:5 - cgroup2 cgroup2 rw,nsdelegate
> 26 24 0:21 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:6 - cgroup cgroup rw,xattr,name=systemd
> 27 14 0:22 / /sys/fs/bpf rw,nosuid,nodev,noexec,relatime shared:7 - bpf bpf rw,mode=700
> 28 14 0:7 / /sys/kernel/debug rw,nosuid,nodev,noexec,relatime shared:14 - debugfs debugfs rw
> 29 14 0:12 / /sys/kernel/config rw,nosuid,nodev,noexec,relatime shared:15 - configfs configfs rw
> 30 21 0:23 / /tmp rw,nosuid,nodev shared:16 - tmpfs tmpfs rw
> 31 21 0:24 / /var/volatile rw,relatime shared:17 - tmpfs tmpfs rw
>
> 4. xino_auto
>
> 5. file in ro is correct
> 6. file in rw is correct
> 7. but the file in overlayfs is  incorrect
>
> What's the reason for this?

I suppose lower squashfs was recreated and mounted with an existing
upper dir that already contains upper files with origin references to the
old squashfs lower fs.

> Can you give some help and suggestions to solve this problem?

Cherry-pick this fix to your kernel:
a888db310195 ovl: fix regression with re-formatted lower squashfs

OR as a workaround, build the lower squashfs with the "-no-exports"
mksquashfs option.

Thanks,
Amir.

       reply	other threads:[~2021-04-15 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6312af55.47e2.178d53227d0.Coremail.ouyangxuan10@163.com>
2021-04-15 17:09 ` Amir Goldstein [this message]
     [not found]   ` <29d44208.9fc.178d85082a4.Coremail.ouyangxuan10@163.com>
     [not found]     ` <32845770.3a85.179127be38c.Coremail.ouyangxuan10@163.com>
2021-04-27  9:22       ` Amir Goldstein

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=CAOQ4uxgPq9E9xxwU2CDyHy-_yCZZeymg+3n+-6AqkGGE1YtwvQ@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=kevin@kevinlocke.name \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=ouyangxuan10@163.com \
    --subject='Re: [kernel]:overlayfs: invalid origin (root/bmcweb_persistent_data.json, ftype=8000, origin ftype=4000)' \
    /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

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).