search for: overlayfs

...rom standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. This release, which is based on the RHEL 7.4 source code (https://seven.centos.org/2017/08/centos-linux-7-1708-based-on-rhel-7-4-source-code/), includes an updated kernel that supports overlayfs container storage, among other enhancements. CentOS Atomic Host includes these core component versions: * atomic-1.18.1-3.1.git0705b1b.el7.x86_64 * cloud-init-0.7.9-9.el7.centos.2.x86_64 * docker-1.12.6-48.git0fdc778.el7.centos.x86_64 * etcd-3.1.9-2.el7.x86_64 * flannel-0.7.1-2.el7.x86_64 * kerne...

...rote: > Date: Thu, 30 Nov 2017 09:55:58 +0100 > On Wed, Nov 29, 2017 at 10:23 PM, <m.roth at 5-cent.us> wrote: > >> The latter would explain the message my user's job gave him when it tried >> to umount / >> >> A bit of googling, and I see something called overlayFS can be used... but >> I know nothing about that, or how dangerous it is. Anyone got a pointed >> to something more than the minimal how to configure docker to use it? >> > You could follow CentOS Atomic SIG > https://wiki.centos.org/SpecialInterestGroup/Atomic > http://w...

...5600686-05:00" level=warning msg="devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem will be ignored." The latter would explain the message my user's job gave him when it tried to umount / A bit of googling, and I see something called overlayFS can be used... but I know nothing about that, or how dangerous it is. Anyone got a pointed to something more than the minimal how to configure docker to use it? mark

Dear all, I'm moving my first baby steps with libvirt-lxc trying to convert over from an LXD installation and one of the hurdles is putting together an image. All the examples I found about libvirt-lxc refer to running /bin/sh in a container, almost as if it was docker, as opposed to run a "full system" like I've been doing with lxd. Also virt-install, often referred in libvirt

...announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. New CentOS Atomic Host with OverlayFS Storage (Jason Brooks) 2. CESA-2017:2789 Moderate CentOS 6 samba Security Update (Johnny Hughes) 3. CESA-2017:2791 Moderate CentOS 6 samba4 Security Update (Johnny Hughes) 4. CESA-2017:2788 Important CentOS 7 augeas Security Update (Johnny Hughes) 5. CESA-2017:2790 Mod...

...c Biggers <ebiggers at google.com> L: linux-fscrypt at vger.kernel.org S: Supported F: common/encrypt FS-IDMAPPED +R: Christian Brauner <brauner at kernel.org> L: linux-fsdevel at vger.kernel.org S: Supported F: src/vfs/ @@ -163,6 +167,7 @@ S: Supported F: tests/ocfs2/ OVERLAYFS +R: Amir Goldstein <amir73il at gmail.com> L: linux-unionfs at vger.kernel.org S: Supported F: tests/overlay @@ -174,6 +179,7 @@ S: Supported F: tests/udf/ XFS +R: Darrick J. Wong <djwong at kernel.org> L: linux-xfs at vger.kernel.org S: Supported F: common/dump -- 2.39.2

...te a chroot with the operating system install you want to run. I've previously tested with a Fedora chroot: https://www.berrange.com/posts/2013/08/12/running-a-full-fedora-os-inside-a-libvirt-lxc-guest/ If you want to have layered modifications, then the best bet is probably to make use of overlayfs with your chroots. ie populate a base chroot and treat it as read-only thereafter. Then create a new directory mounted with overlayfs to add a writable layer on top. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org...

Oliver Welter: > >after upgrading my mail server (dovecot 1.1.7 -> 2.2.13) I get tons of > >messages about corrupted index files in the syslog ("Error: Corrupted > >transaction log" and "Warning: fscking index file .. dovecot.index". > > > Some more debugging - I did a "fuser" on a broken dovecot.index file > and see a lot of stale

...fscrypt at vger.kernel.org +S: Supported +F: common/encrypt + +FS-IDMAPPED +L: linux-fsdevel at vger.kernel.org +S: Supported +F: src/vfs/ + +NFS +L: linux-nfs at vger.kernel.org +S: Supported +F: tests/nfs/ +F: common/nfs + +OCFS2 +L: ocfs2-devel at oss.oracle.com +S: Supported +F: tests/ocfs2/ + +OVERLAYFS +L: linux-unionfs at vger.kernel.org +S: Supported +F: tests/overlay +F: common/overlay + +UDF +R: Jan Kara <jack at suse.com> +S: Supported +F: tests/udf/ + +XFS +L: linux-xfs at vger.kernel.org +S: Supported +F: common/dump +F: common/fuzzy +F: common/inject +F: common/populate +F: common/r...

...em install you want to run. > > I've previously tested with a Fedora chroot: > > > https://www.berrange.com/posts/2013/08/12/running-a-full-fedora-os-inside-a-libvirt-lxc-guest/ > > If you want to have layered modifications, then the best bet is probably > to make use of overlayfs with your chroots. ie populate a base chroot > and treat it as read-only thereafter. Then create a new directory mounted > with overlayfs to add a writable layer on top. > > > Regards, > Daniel > -- > |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/...

...d be: > > mkdir /A/FolderB > mount --bind /A/FolderA /A/FolderB > > Then just exclude /A/FolderA from the rsync and you are done. This does > mean that you have to be ok with /A/FolderB existing on the source. > > > The second option would be to use somthing like aufs or overlayfs to > create a new mountpoint that contains everything you want and perhaps with > a little bit of mount --bind thrown in. > > > I just saw your response, and and what you describe makes sense. Sounds > like the mount bind option + exclude might be the most elegant option for >...

As part of the oVirt Node[1] project, I'm going to P.O.C. a version of the node using febootstrap 2.x instead of livecd-creator. The main reasons in doing this is for allowing a r/w root filesystem without some hacky overlayfs and just to see if it can be done. On IRC, rwmjones mentioned a few issues he ran into with febootstrap 2.x where some rpms had %post scripts which aren't really safe inside a chroot. It would be nice to get some more detail as to what problems exactly have been encountered and what is the best...

...w ctime accessors nilfs2: switch to new ctime accessors ntfs: switch to new ctime accessors ntfs3: switch to new ctime accessors ocfs2: switch to new ctime accessors omfs: switch to new ctime accessors openpromfs: switch to new ctime accessors orangefs: switch to new ctime accessors overlayfs: switch to new ctime accessors proc: switch to new ctime accessors pstore: switch to new ctime accessors qnx4: switch to new ctime accessors qnx6: switch to new ctime accessors ramfs: switch to new ctime accessors reiserfs: switch to new ctime accessors romfs: switch to new ctime acce...

...g owncloud 9.1.1 EL7 release in EPEL7 will be removing my workaround and require this for full correct functionality. In the tech preview world nftables joins the testing group (I'll have articles up exploring this new firewalling method in the coming weeks) for networking. Whilst with storage overlayfs and btrfs remain in tech preview status - with cephfs joining them... as notable pieces. There's also new pNFS stuff. This is only a small snippet of things that jumped out relevant to me personally. As always make sure you read through the release notes in full. to be ready once CentOS starts...

I may have missed some overnight replies to my question from yesterday - if so, sorry. >From my googling, it looks like I should change from the loopback device to overlayFS (with overlay2). What I haven't found is, first and foremost, more clarity on configuring storage. It *appears* that the loopback storage is just a directory under /var/lib/docker (yet I see a reference in someone's blog to ~docker - *is* /var/lib/docker intended as ~docker? Can I make a...

...r used by Docker. This issue doesn't show with the centos:7 container. It already comes with the "fastestmirror" and "ovl" plugins installed. The "ovl" plugin is a workaround to avoid this corruption. See the bottom of https://docs.docker.com/storage/storagedriver/overlayfs-driver/ for more details. Fedora 29 and 30 already have an equivalent "dnf-plugin-ovl" package ( https://src.fedoraproject.org/rpms/dnf-plugin-ovl). However, I couldn't find it for RHEL8 or CentOS 8. I can use the "touch" workaround for now. But are there plans to bring th...

..._mailbox_sync_pos): assertion failed: (file_offset >= log->head->saved_tail_offset)" I tried all offered locking methods (fcntl, flock, dotlock) without success. The server runs inside a virtual guest (linux-vserver which is similar to LXC) using an overlay filesystem. I suspect the overlayfs but have no idea how to test this, besides - as I understand - dotlock should not rely on the fs locking at all :( I even wonder why the old dovecot worked for nearly 10 years without any problems, even under higher loads. The config is pretty straightforward: # 2.2.13: /etc/dovecot/dovecot.conf...

21:51 < foxx> hello! does anyone know if libguestfs supports any sort of COW (copy on write) functionality? for example, if i mount an image which is RO, can i make it write any changes out to a higher dir (such as how overlayfs/aufs works) The answer is yes. Create a qcow2 overlay on top of your image before starting: qemu-img create -b original.img -f qcow2 overlay.qcow2 guestfish -a overlay.qcow2 [etc] Changes are written to overlay.qcow2. The original is not modified. You can also display diff...

...derB >> mount --bind /A/FolderA /A/FolderB >> >> Then just exclude /A/FolderA from the rsync and you are done. This does >> mean that you have to be ok with /A/FolderB existing on the source. >> >> >> The second option would be to use somthing like aufs or overlayfs to >> create a new mountpoint that contains everything you want and perhaps with >> a little bit of mount --bind thrown in. >> >> >> I just saw your response, and and what you describe makes sense. Sounds >> like the mount bind option + exclude might be the most...

...s/nfs3_fs.h | 1 - fs/nfs/nfs3acl.c | 6 -- fs/nfs/nfs3super.c | 3 - fs/nfsd/nfs4xdr.c | 3 +- fs/ntfs3/xattr.c | 4 -- fs/ocfs2/xattr.c | 41 +++++++------ fs/orangefs/xattr.c | 2 - fs/overlayfs/super.c | 8 --- fs/posix_acl.c | 20 ------- fs/reiserfs/xattr.c | 38 ++++++------ fs/xattr.c | 124 ++++++++++++++++++++-------------------- fs/xfs/xfs_xattr.c | 4 -- include/linux/posix_acl_xattr.h | 6 +- includ...