From: Hongxu Jia <hongxu.jia@windriver.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: aufs missing in kernel 4.4
Date: Thu, 31 Mar 2016 18:31:16 +0800 [thread overview]
Message-ID: <56FCFC74.4080001@windriver.com> (raw)
In-Reply-To: <56FCF6E3.7090109@windriver.com>
On 03/31/2016 06:07 PM, Hongxu Jia wrote:
> Hi Bruce,
>
> In kernel 4.1, it supports aufs:
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.1/tree/fs/aufs?h=standard/base
>
>
> But it does not exist in kernel 4.4:
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-4.4/tree/fs?h=standard/base
>
>
> It caused ISO's rootfs is readonly.
>
> In meta/recipes-core/initrdscripts/files/init-live.sh:
> -----------------
> 174 elif grep -q -w "aufs" /proc/filesystems; then
> 175 union_fs_type="aufs"
> [snip]
> 204 "aufs")
> 205 mkdir -p /rootfs.ro /rootfs.rw
> 206 if ! mount -n --move $ROOT_MOUNT /rootfs.ro; then
> 207 rm -rf /rootfs.ro /rootfs.rw
> 208 fatal "Could not move rootfs mount point"
> 209 else
> 210 mount -t tmpfs -o rw,noatime,mode=755 tmpfs
> /rootfs.rw
> 211 mount -t aufs -o
> "dirs=/rootfs.rw=rw:/rootfs.ro=ro" aufs $ROOT_MOUNT
> 212 mkdir -p $ROOT_MOUNT/rootfs.ro $ROOT_MOUNT/rootfs.rw
> 213 mount --move /rootfs.ro $ROOT_MOUNT/rootfs.ro
> 214 mount --move /rootfs.rw $ROOT_MOUNT/rootfs.rw
> 215 fi
> 216 ;;
> -----------------
>
> Would you please update kernel 4.4 to support aufs?
Or with Robert's patch in mailing list also could fix this issue.
[OE-core] [PATCH 1/1] linux-yocto 4.4: enable overlayfs
//Hongxu
>
> //Hongxu
>
next prev parent reply other threads:[~2016-03-31 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 10:07 aufs missing in kernel 4.4 Hongxu Jia
2016-03-31 10:31 ` Hongxu Jia [this message]
2016-03-31 12:06 ` Bruce Ashfield
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=56FCFC74.4080001@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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