All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: Johannes Hirte <johannes.hirte@datenkhaos.de>
Cc: "xavier.gnata@gmail.com" <xavier.gnata@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: "Btrfs: device_list_add() should not update list when mounted" breaks subvol mount
Date: Wed, 17 Sep 2014 16:49:18 +0800	[thread overview]
Message-ID: <54194B0E.6080603@oracle.com> (raw)
In-Reply-To: <20140913232320.64fd189c@datenkhaos.de>



>> And now I was able to reproduce on a second machine. The main
>> difference between the affected and the unaffected systems is
>> initramfs. On the affected systems, I don't use one.

  In this test of with or without initramfs script. I guess the kernel
  remain same at 3.17-rc3 and above

>> On the working
>> systems, the rootfs is mounted via initramfs before. I'll test, if an
>> initramfs will solve the issue. Seems likely, cause if I put the disk
>> of an affected system into a working system and mount it there,
>> everything works.
>
> Of course, with the initramfs it works. Content of the init-script:
>
> #!/bin/sh
>
> mount -t devtmpfs devtmpfs /dev
> mount -t proc proc /proc
> mount -t sysfs sysfs /sys
> mount -t tmpfs tmpfs /run
> sleep 3  # wait for kernel msgs to quiet
>
> echo "loading initrd"
>
> btrfs dev scan
> sleep 5
>
> mount -o ro,subvol=rootfs,inode_cache,autodefrag /dev/sda1 /newroot

  this will work since the device path that we provide here
  is already the device path which probably will be the final
  device path after bootup.

Thanks

> if [[ -x /newroot/sbin/init ]]; then
>          umount /sys /proc
>          exec switch_root /newroot /sbin/init
> fi
>
> #rescue shell
> exec sh


  parent reply	other threads:[~2014-09-17  8:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 22:22 "Btrfs: device_list_add() should not update list when mounted" breaks subvol mount Johannes Hirte
2014-09-10 23:26 ` Anand Jain
2014-09-11  2:37 ` Anand Jain
2014-09-12 20:43   ` xavier.gnata
2014-09-13  5:36     ` Anand Jain
2014-09-13 17:55       ` Johannes Hirte
2014-09-13 21:23         ` Johannes Hirte
2014-09-14  0:45           ` Duncan
2014-09-15 17:13             ` Johannes Hirte
2014-09-15 12:32           ` Anand Jain
2014-09-15 17:14             ` Johannes Hirte
2014-09-15 17:39               ` Anand Jain
2014-09-15 22:17                 ` Johannes Hirte
2014-09-16 21:55                   ` Anand Jain
2014-09-17  8:49           ` Anand Jain [this message]
2014-09-14 11:12       ` xavier.gnata

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=54194B0E.6080603@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=johannes.hirte@datenkhaos.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=xavier.gnata@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.