Am 21.07.2011 20:51, schrieb Jeff Spaleta: > is there a problem with bind mount handling? Yes Was it caught in > testing? Seems like it wasn't. Does Fedora make any effort to test > bind mounts as part of organized pre-release QA? I'm not aware that we > do as our pre-release QA is quite narrowly scoped to ensure default > install configs as we don't have the resources to test all possible > configurations and command options. * bind-chroot-9.8.0-7.P4.fc15.x86_64 is a untouched fedora-package * so fedora is ACTIVE creating bind-mounts * /bin/df is a core utility and throws error * /bin/mount is a core utility * /bin/mount has NO information about a bind-mount so if "/proc/mounts" is the kernel-layer why do it not contain any hint what is a physical device and hwat are bind-mounts? in other words: HOW get the information? from my point of view i would have no idea how anybody should fix /bin/df or /bin/mount if /proc/mounts has no informations for the userland what is going on on the system ________________ here is nothing manually changed, this is DEFAULT-SETUP: /bin/df with a running named: /bin/df: „/var/named/chroot/etc/named“: Keine Berechtigung /bin/df: „/var/named/chroot/usr/lib64/bind“: Keine Berechtigung /bin/df: „/var/named/chroot/etc/named.iscdlv.key“: Keine Berechtigung /bin/df: „/var/named/chroot/etc/named.root.key“: Keine Berechtigung /bin/mount | grep /dev/sda2 /dev/sda2 on / type ext4 (rw,noatime,nodiratime,nouser_xattr,noacl,commit=60,barrier=0,journal_async_commit,data=writeback,inode_readahead_blks=64) /dev/sda2 on /var/named/chroot/etc/named type ext4 (rw,noatime,nodiratime,nouser_xattr,noacl,commit=60,barrier=0,journal_async_commit,data=writeback,inode_readahead_blks=64) /dev/sda2 on /var/named/chroot/usr/lib64/bind type ext4 (rw,noatime,nodiratime,nouser_xattr,noacl,commit=60,barrier=0,journal_async_commit,data=writeback,inode_readahead_blks=64) /dev/sda2 on /var/named/chroot/etc/named.iscdlv.key type ext4 (rw,noatime,nodiratime,nouser_xattr,noacl,commit=60,barrier=0,journal_async_commit,data=writeback,inode_readahead_blks=64) /dev/sda2 on /var/named/chroot/etc/named.root.key type ext4 (rw,noatime,nodiratime,nouser_xattr,noacl,commit=60,barrier=0,journal_async_commit,data=writeback,inode_readahead_blks=64) the permanently raising number of all sorts of "tmpfs" makes the output of "df" also not better readable and their size of 4GB on a machine with 8GB pyhiscal memory makes my look also critical udev devtmpfs 3,9G 0 3,9G 0% /dev tmpfs tmpfs 1,0G 204K 1,0G 1% /dev/shm tmpfs tmpfs 4,0G 3,0M 4,0G 1% /run tmpfs tmpfs 4,0G 0 4,0G 0% /sys/fs/cgroup tmpfs tmpfs 4,0G 3,0M 4,0G 1% /var/lock tmpfs tmpfs 4,0G 3,0M 4,0G 1% /var/run tmpfs tmpfs 4,0G 0 4,0G 0% /media
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
