[atomic-wg] Issue #320: btrfs info: bind mounts cause bogus subvol
information in mountinfo
by Chris Murphy
chrismurphy reported a new issue against the project: `atomic-wg` that you are following:
``
This is an info bug, not an atomic bug, and it's non-fatal. Open question if upstream should be pushed to fix it or if this is cosmetic.
Background: Btrfs subvolumes can be directly mounted with `mount -o subvol=nameofsubvolume`. Behind the scenes this is a bind mount. When using the mount command or looking at `/proc/self/mountinfo` both subvolid and subvol info is shown.
Example:
`/dev/sda1 on /srv/scratch type btrfs (rw,noatime,seclabel,compress=zlib,space_cache,subvolid=910,subvol=/scratch,x-systemd.automount)`
subvolid=910 is subvol=scratch, those are synonymous and immutable, at least on disk.
Problem: Ostree installations make prolific use of bind mounts for assembly, and I've discovered that mount thinks these bind mounts are subvolumes.
Example:
```
/dev/sda7 on /sysroot type btrfs (rw,relatime,seclabel,ssd,space_cache,subvolid=258,subvol=/root)
/dev/sda7 on / type btrfs (rw,relatime,seclabel,ssd,space_cache,subvolid=258,subvol=/root/ostree/deploy/fedora-workstation/deploy/cee1dd51ce63436e3d2e9df8b1759981055c7ac29c78d450217bf684631f0549.0)
/dev/sda7 on /usr type btrfs (ro,relatime,seclabel,ssd,space_cache,subvolid=258,subvol=/root/ostree/deploy/fedora-workstation/deploy/cee1dd51ce63436e3d2e9df8b1759981055c7ac29c78d450217bf684631f0549.0/usr)
/dev/sda7 on /var type btrfs (rw,relatime,seclabel,ssd,space_cache,subvolid=258,subvol=/root/ostree/deploy/fedora-workstation/var)
```
The first line is correct. subvolid=5 is subvol=root. All the other lines have correct subvolid's but the subvol listed is a bind mount, there is no such subvolume as those listed.
Clearly the kernel code is correctly looking up subvolume ID, but it's assuming bind mounts are subvolumes rather than directly looking them up. Upstream report is here:
https://www.spinics.net/lists/linux-btrfs/msg67410.html
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/320
6 years, 8 months
Fedora Atomic WG Meeting Minutes 2017-08-09
by Dusty Mabe
summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-09/fedora_atom...
full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-09/fedora_atom...
===================================
#fedora-meeting-1: fedora_atomic_wg
===================================
Meeting started by dustymabe at 17:00:28 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-09/fedora_atom...
.
Meeting summary
---------------
* roll call (dustymabe, 17:00:34)
* previous meeting action items (dustymabe, 17:04:26)
* dusty created https://pagure.io/atomic-wg/issue/311 to track RFE for
rawhide based containers to be made available from
registry.fedoraproject.org (dustymabe, 17:04:52)
* dusty created https://pagure.io/atomic-wg/issue/312 for
experimenting with modularity (dustymabe, 17:05:04)
* dusty created https://pagure.io/atomic-wg/issue/313 for open
questions for modularity team and jbrooks is helping create a list
of questions (dustymabe, 17:05:24)
* ACTION: jberkus strigazi to continue moving kube issues to new
kube-sig tracker (dustymabe, 17:07:33)
* questions for the modularity team (dustymabe, 17:08:06)
* LINK: https://pagure.io/atomic-wg/issue/313 (dustymabe, 17:08:16)
* ACTION: jbrooks to look at building a module himself, this will help
us come up with even more questions before our meeting next week
(dustymabe, 17:13:22)
* ACTION: dustymabe to invite petr sabata to the atomic host meeting
next week to answer questions and to present a POC atomic host from
a module (dustymabe, 17:13:47)
* containerized kubernetes in f26 atomic host (dustymabe, 17:16:38)
* ACTION: jbrooks to go through 'remove-kube' tickets and update them
(dustymabe, 17:25:00)
* open floor (dustymabe, 17:28:17)
* LINK:
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-A...
(dustymabe, 17:29:30)
* ACTION: kushal to create ticket for planning our activities around
FLOCK (dustymabe, 17:31:40)
* LINK:
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-A...
(dustymabe, 17:31:52)
* maxamillion hopes to get a container release out tomorrow
(dustymabe, 17:37:16)
Meeting ended at 17:39:11 UTC.
Action Items
------------
* jberkus strigazi to continue moving kube issues to new kube-sig
tracker
* jbrooks to look at building a module himself, this will help us come
up with even more questions before our meeting next week
* dustymabe to invite petr sabata to the atomic host meeting next week
to answer questions and to present a POC atomic host from a module
* jbrooks to go through 'remove-kube' tickets and update them
* kushal to create ticket for planning our activities around FLOCK
Action Items, by person
-----------------------
* dustymabe
* dustymabe to invite petr sabata to the atomic host meeting next week
to answer questions and to present a POC atomic host from a module
* jbrooks
* jbrooks to look at building a module himself, this will help us come
up with even more questions before our meeting next week
* jbrooks to go through 'remove-kube' tickets and update them
* kushal
* kushal to create ticket for planning our activities around FLOCK
* **UNASSIGNED**
* jberkus strigazi to continue moving kube issues to new kube-sig
tracker
People Present (lines said)
---------------------------
* dustymabe (111)
* maxamillion (41)
* jbrooks (40)
* zodbot (16)
* kushal (7)
* ksinny (6)
* _ari_ (2)
* nzwulfin (1)
* sayan (1)
* bowlofeggs (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 8 months
Re: Fedora Atomic Host Two Week Release Announcement
by Dusty Mabe
On 08/08/2017 03:41 PM, noreply(a)fedoraproject.org wrote:
>
> A new Fedora Atomic Host update is available via an OSTree commit:
>
> Commit: f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6
> Version: 26.101
>
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-26-2017...
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-26-2017...
>
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
>
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
>
> For more information about the latest targets, please reference the Fedora
> Cloud Wiki space.
>
> https://fedoraproject.org/wiki/Cloud#Quick_Links
>
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
>
> Thank you,
> Fedora Release Engineering
>
Note that the qcow and vagrant images from last release were following
the wrong ref in the OSTree repository. If you used that media then please
make sure you are following the `fedora/26/x86_64/atomic-host` ref. See
https://pagure.io/atomic-wg/issue/307 for more details.
The diff between this and the previous released version is:
ostree diff commit old: 0715ce81064c30d34ed52ef811a3ad5e5d6a34da980bf35b19312489b32d9b83
ostree diff commit new: f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6
Upgraded:
GeoIP-GeoLite-data 2017.06-1.fc26.noarch -> 2017.07-1.fc26.noarch
cockpit-bridge 143-1.fc26.x86_64 -> 147-1.fc26.x86_64
cockpit-docker 143-1.fc26.x86_64 -> 147-1.fc26.x86_64
cockpit-networkmanager 143-1.fc26.noarch -> 147-1.fc26.noarch
cockpit-ostree 143-1.fc26.x86_64 -> 147-1.fc26.x86_64
cockpit-system 143-1.fc26.noarch -> 147-1.fc26.noarch
container-selinux 2:2.20-2.fc26.noarch -> 2:2.21-1.fc26.noarch
criu 3.2.1-2.fc26.x86_64 -> 3.3-2.fc26.x86_64
curl 7.53.1-8.fc26.x86_64 -> 7.53.1-9.fc26.x86_64
dbus 1:1.11.14-1.fc26.x86_64 -> 1:1.11.16-1.fc26.x86_64
dbus-libs 1:1.11.14-1.fc26.x86_64 -> 1:1.11.16-1.fc26.x86_64
dhcp-client 12:4.3.5-7.fc26.x86_64 -> 12:4.3.5-9.fc26.x86_64
dhcp-common 12:4.3.5-7.fc26.noarch -> 12:4.3.5-9.fc26.noarch
dhcp-libs 12:4.3.5-7.fc26.x86_64 -> 12:4.3.5-9.fc26.x86_64
file 5.30-6.fc26.x86_64 -> 5.30-8.fc26.x86_64
file-libs 5.30-6.fc26.x86_64 -> 5.30-8.fc26.x86_64
glusterfs 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
glusterfs-client-xlators 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
glusterfs-fuse 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
glusterfs-libs 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
gnupg 1.4.21-2.fc26.x86_64 -> 1.4.22-1.fc26.x86_64
gomtree 0.3.1-1.fc26.x86_64 -> 0.4.0-1.fc26.x86_64
iputils 20161105-2.fc26.x86_64 -> 20161105-5.fc26.x86_64
krb5-libs 1.15.1-15.fc26.x86_64 -> 1.15.1-17.fc26.x86_64
libcurl 7.53.1-8.fc26.x86_64 -> 7.53.1-9.fc26.x86_64
libidn2 2.0.2-1.fc26.x86_64 -> 2.0.3-1.fc26.x86_64
libselinux 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libselinux-python 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libselinux-python3 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libselinux-utils 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libsepol 2.6-1.fc26.x86_64 -> 2.6-2.fc26.x86_64
libsolv 0.6.28-1.fc26.x86_64 -> 0.6.28-5.fc26.x86_64
libsss_idmap 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
libsss_nss_idmap 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
libsss_sudo 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
nfs-utils 1:2.1.1-5.rc4.fc26.x86_64 -> 1:2.1.1-5.rc5.fc26.x86_64
nmap-ncat 2:7.40-5.fc26.x86_64 -> 2:7.40-7.fc26.x86_64
nspr 4.14.0-2.fc26.x86_64 -> 4.15.0-1.fc26.x86_64
nss 3.30.2-1.1.fc26.x86_64 -> 3.31.0-1.1.fc26.x86_64
nss-softokn 3.30.2-1.0.fc26.x86_64 -> 3.31.0-1.0.fc26.x86_64
nss-softokn-freebl 3.30.2-1.0.fc26.x86_64 -> 3.31.0-1.0.fc26.x86_64
nss-sysinit 3.30.2-1.1.fc26.x86_64 -> 3.31.0-1.1.fc26.x86_64
nss-tools 3.30.2-1.1.fc26.x86_64 -> 3.31.0-1.1.fc26.x86_64
nss-util 3.30.2-1.0.fc26.x86_64 -> 3.31.0-1.0.fc26.x86_64
oci-register-machine 0-3.8.gitbf6b0f2.fc26.x86_64 -> 0-3.10.gitcbf1b8f.fc26.x86_64
ostree 2017.8-3.fc26.x86_64 -> 2017.9-2.fc26.x86_64
ostree-grub2 2017.8-3.fc26.x86_64 -> 2017.9-2.fc26.x86_64
ostree-libs 2017.8-3.fc26.x86_64 -> 2017.9-2.fc26.x86_64
pcre2 10.23-8.fc26.x86_64 -> 10.23-9.fc26.x86_64
policycoreutils 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
policycoreutils-python 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
policycoreutils-python-utils 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
policycoreutils-python3 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
python3-sssdconfig 1.15.2-5.fc26.noarch -> 1.15.3-1.fc26.noarch
rpm-ostree 2017.6-3.fc26.x86_64 -> 2017.7-1.fc26.x86_64
runc 1:1.0.0-9.git6394544.fc26.x86_64 -> 1:1.0.1-1.gitc5ec254.fc26.x86_64
selinux-policy 3.13.1-260.1.fc26.noarch -> 3.13.1-260.3.fc26.noarch
selinux-policy-targeted 3.13.1-260.1.fc26.noarch -> 3.13.1-260.3.fc26.noarch
skopeo 0.1.22-1.git5d24b67.fc26.x86_64 -> 0.1.23-2.git1bbd87f.fc26.x86_64
skopeo-containers 0.1.22-1.git5d24b67.fc26.x86_64 -> 0.1.23-2.git1bbd87f.fc26.x86_64
sssd-client 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
tmux 2.3-2.fc26.x86_64 -> 2.5-1.fc26.x86_64
vim-minimal 2:8.0.728-1.fc26.x86_64 -> 2:8.0.823-1.fc26.x86_64
Significant updates in this release are ostree, rpm-ostree, cockpit and selinux.
The Vagrant Cloud page with the new atomic host:
https://app.vagrantup.com/fedora/boxes/26-atomic-host
https://app.vagrantup.com/fedora/boxes/26-atomic-host/versions/26.20170807.0
For posterity the AMIs for this release are:
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-northeast-1) ami-3623c850 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-1) ami-df0c95bc hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-2) ami-1f2e377c hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-central-1) ami-df822cb0 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-west-1) ami-fd3fc984 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (sa-east-1) ami-0d97e161 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-east-1) ami-d82f00a3 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-1) ami-e8341f88 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-2) ami-20d43558 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-northeast-1) ami-9a2ec5fc hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-1) ami-3c0c955f hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-2) ami-6a2f3609 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-central-1) ami-ea802e85 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-west-1) ami-823ccafb hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (sa-east-1) ami-0e97e162 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-east-1) ami-5f2f0024 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-1) ami-d1311ab1 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-2) ami-13d7366b hvm standard
Dusty
6 years, 8 months