Re: Restore backup to KVM

From	solitone <solitone@mail.com>
Newsgroups	linux.debian.user
Subject	Re: Restore backup to KVM
Date	2017-09-29 06:40 +0200
Message-ID	<uuVfH-1vc-7@gated-at.bofh.it> (permalink)
References	(6 earlier) <uu41J-zi-43@gated-at.bofh.it> <uueu6-7gi-13@gated-at.bofh.it> <uujk6-2b5-7@gated-at.bofh.it> <uunQK-5FA-15@gated-at.bofh.it> <uuAXD-5v7-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 28/09/17 08:58, Reco wrote:
> It's initrd that first tries to mount tmpfs filesystems on /root (and
> fails), and only *then* mounts your root filesystem to /root (with the
> intention to switch to it as /).

Is the stock initrd supposed to work like this? When I boot my 
production system, I end up with tmpfs mounted on /run:

$ df
Filesystem       1K-blocks      Used  Available Use% Mounted on
udev               4027784         0    4027784   0% /dev
tmpfs               807952      1352     806600   1% /run
/dev/sda5         85825416  58793224   22629416  73% /
tmpfs              4039744      4972    4034772   1% /dev/shm
tmpfs                 5120         4       5116   1% /run/lock
tmpfs              4039744         0    4039744   0% /sys/fs/cgroup
/dev/sda1           201633     23678     177955  12% /boot/efi
tmpfs               807948         0     807948   0% /run/user/113
tmpfs               807948        20     807928   1% /run/user/1000

Also, I don't understand why it needs to mount the root filesystem to /root.

Thread

Restore backup to KVM solitone <solitone@mail.com> - 2017-09-22 06:50 +0200
  Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-22 08:10 +0200
    Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-22 21:20 +0200
      Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-22 21:40 +0200
        Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-24 11:00 +0200
          Re: Restore backup to KVM <tomas@tuxteam.de> - 2017-09-24 11:20 +0200
          Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-24 12:00 +0200
            Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-25 21:10 +0200
              Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 08:50 +0200
            Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-25 21:20 +0200
              Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 08:50 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 13:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 13:20 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 17:40 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 21:20 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 21:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-27 09:00 +0200
                Re: Restore backup to KVM "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-27 09:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-27 10:40 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-27 14:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-27 19:00 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-28 09:00 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-29 06:40 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-29 08:40 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-30 13:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-30 15:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-30 17:00 +0200

csiph-web