Util-Linux package development
 help / color / mirror / Atom feed
From: Stanislav Brabec <sbrabec@suse.cz>
To: util-linux@vger.kernel.org, David Sterba <dsterba@suse.cz>
Subject: another mount -a problem, not related to btrfs
Date: Wed, 10 Feb 2016 17:03:16 +0100	[thread overview]
Message-ID: <56BB5F44.6070208@suse.cz> (raw)
In-Reply-To: <56B23240.8060405@suse.cz>


Dne 3.2.2016 v 18:00 Stanislav Brabec napsal(a):
> Stanislav Brabec wrote:
>> (rw,relatime,space_cache,subvolid=258,subvol=/d0/dd0/ddd0/d2/dd2/ddd2/s3/bind-mnt)
>>
>
> After a discussion with David, we came to the conclusion that the
> problem is caused by bug in the mountinfo provided by kernel:
>
While working on a fix, I found a new bug, not related to btrfs:

truncate -s10M source.img
mkdir -p /source/subdir
mkdir -p /dest
/sbin/mkfs.ext4 source.img
losetup /dev/loop0 $PWD/source.img
echo "/dev/loop0 /source ext4 defaults 0 0" >>/etc/fstab
mount -a
mkdir -p /source/subdir
mount -o bind /source /dest
echo "/source/subdir /dest auto bind 0 0" >>/etc/fstab
mount -a

Got:
/dev/loop0 on /source type ext4 (rw,relatime,data=ordered)
/dev/loop0 on /dest type ext4 (rw,relatime,data=ordered)
/dev/loop0 on /dest type ext4 (rw,relatime,data=ordered)
/dev/loop0 on /source type ext4 (rw,relatime,data=ordered)
and empty /source

It apparently should not happen.

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                         e-mail: sbrabec@suse.com
Lihovarská 1060/12                            tel: +49 911 7405384547
190 00 Praha 9                                 fax:  +420 284 084 001
Czech Republic                                    http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76

  parent reply	other threads:[~2016-02-10 16:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 18:00 [PATCH] tests: add btrfs mount tests Stanislav Brabec
2016-02-02 20:14 ` [PATCH] tests: add btrfs mount tests (fails!) Stanislav Brabec
2016-02-03 17:00   ` Stanislav Brabec
2016-02-03 18:39     ` Stanislav Brabec
2016-02-10 16:03     ` Stanislav Brabec [this message]
2016-02-11  9:43   ` Karel Zak
2016-02-11 13:47     ` Stanislav Brabec
2016-02-11 16:34       ` Stanislav Brabec
2016-02-11 18:07         ` [PATCH] tests: add btrfs mount tests Stanislav Brabec
2016-02-12  9:38           ` Karel Zak
2016-02-12 10:07         ` [PATCH] tests: add btrfs mount tests (fails!) Karel Zak
2016-02-19 15:02       ` Stanislav Brabec
2016-03-09 19:13         ` Stanislav Brabec
2016-03-14  1:20 ` [PATCH] tests: add btrfs mount tests Ruediger Meier
2016-03-14 14:19   ` Stanislav Brabec
2016-03-14 23:27     ` Ruediger Meier

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=56BB5F44.6070208@suse.cz \
    --to=sbrabec@suse.cz \
    --cc=dsterba@suse.cz \
    --cc=util-linux@vger.kernel.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