arch-chroot : duplicate mounts after mounting a folder with --bind option

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I'm chrooting in an arch systeml calling :



sudo arch-chroot -u ctag:ctag .


After this call I can see mounts created by arch_chroot :



38,56d37
< /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
< proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
< proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
< sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
< sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
< efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
< efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
< udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
< udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
< devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
< devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
< shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
< shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
< run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
< run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
< tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
< tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
< /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)
< /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)


Why are proc and other mounted twice?



I did an another test, before chrooting I did a bind mount :



sudo mount --bind /home/remi /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/


I chrooted and here are mounts points : 



37a38,76
> /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi type ext4 (rw,relatime,data=ordered)
> /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
> /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
> proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
> proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
> proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
> proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
> sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
> sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
> sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
> sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
> efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
> efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
> efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
> efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
> udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
> udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
> udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
> udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
> devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
> shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
> shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
> shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
> run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
> tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
> tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
> tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)


There is still duplicate mounts, but some other mounts to previously mounted /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/



How can we explain that?



After exiting chroot, these mounts points are unmounted.




arch-linux chroot




share|improve this question
























    up vote
    0
    down vote

    favorite












    I'm chrooting in an arch systeml calling :



    sudo arch-chroot -u ctag:ctag .


    After this call I can see mounts created by arch_chroot :



    38,56d37
    < /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
    < proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
    < proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
    < sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
    < sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
    < efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    < efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    < udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
    < udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
    < devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    < devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    < shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
    < shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
    < run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    < run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    < tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
    < tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
    < /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)
    < /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)


    Why are proc and other mounted twice?



    I did an another test, before chrooting I did a bind mount :



    sudo mount --bind /home/remi /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/


    I chrooted and here are mounts points : 



    37a38,76
    > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi type ext4 (rw,relatime,data=ordered)
    > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
    > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
    > proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
    > proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
    > proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
    > proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
    > sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
    > sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
    > sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
    > sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
    > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
    > udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
    > udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
    > udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
    > udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
    > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    > shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
    > shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
    > shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
    > shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
    > run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    > run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    > run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    > run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
    > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
    > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
    > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)


    There is still duplicate mounts, but some other mounts to previously mounted /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/



    How can we explain that?



    After exiting chroot, these mounts points are unmounted.




    arch-linux chroot




    share|improve this question






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm chrooting in an arch systeml calling :



      sudo arch-chroot -u ctag:ctag .


      After this call I can see mounts created by arch_chroot :



      38,56d37
      < /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
      < proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      < proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      < sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      < sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      < efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      < efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      < udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      < udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      < devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      < devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      < shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      < shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      < run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      < run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      < tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      < tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      < /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)
      < /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)


      Why are proc and other mounted twice?



      I did an another test, before chrooting I did a bind mount :



      sudo mount --bind /home/remi /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/


      I chrooted and here are mounts points : 



      37a38,76
      > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi type ext4 (rw,relatime,data=ordered)
      > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
      > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)


      There is still duplicate mounts, but some other mounts to previously mounted /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/



      How can we explain that?



      After exiting chroot, these mounts points are unmounted.




      arch-linux chroot




      share|improve this question












      I'm chrooting in an arch systeml calling :



      sudo arch-chroot -u ctag:ctag .


      After this call I can see mounts created by arch_chroot :



      38,56d37
      < /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
      < proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      < proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      < sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      < sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      < efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      < efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      < udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      < udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      < devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      < devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      < shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      < shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      < run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      < run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      < tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      < tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      < /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)
      < /dev/nvme0n1p4 on /home/remi/dev_tools/ti/ccs/ccs_root/etc/resolv.conf type ext4 (rw,relatime,data=ordered)


      Why are proc and other mounted twice?



      I did an another test, before chrooting I did a bind mount :



      sudo mount --bind /home/remi /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/


      I chrooted and here are mounts points : 



      37a38,76
      > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi type ext4 (rw,relatime,data=ordered)
      > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
      > /dev/nvme0n1p6 on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root type ext4 (rw,relatime,data=ordered)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > proc on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/proc type proc (rw,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > sys on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys type sysfs (ro,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > efivarfs on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > udev on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev type devtmpfs (rw,nosuid,relatime,size=16392576k,nr_inodes=4098144,mode=755)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > devpts on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > shm on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/dev/shm type tmpfs (rw,nosuid,nodev,relatime)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > run on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)
      > tmp on /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/tmp type tmpfs (rw,nosuid,nodev)


      There is still duplicate mounts, but some other mounts to previously mounted /home/remi/dev_tools/ti/ccs/ccs_root/home/ctag/host_files_remi/dev_tools/ti/ccs/ccs_root/



      How can we explain that?



      After exiting chroot, these mounts points are unmounted.





      arch-linux chroot





      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 15 '17 at 11:16









      rem

      15817




      15817

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f411029%2farch-chroot-duplicate-mounts-after-mounting-a-folder-with-bind-option%23new-answer', 'question_page');

          );

          Post as a guest






















          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes










           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f411029%2farch-chroot-duplicate-mounts-after-mounting-a-folder-with-bind-option%23new-answer', 'question_page');

          );

          Post as a guest
































































          1kOl0mHcbYvkuPFdYaYGNIc U0RwF W Hf1jdAeor cBZ2T,rZdV015yF S9iH3qHwrtB
          -
          dNO,Rw Bxma,pK zhB4Qxo9NTZvRFe7OD Xb4IRpWk3Z

          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
          Read more

          How many registers does an x86_64 CPU actually have?

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
          Read more

          Displaying single band from multi-band raster using QGIS

          Image
          Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
          Read more