All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: Johannes Hirte <johannes.hirte@datenkhaos.de>,
	linux-btrfs@vger.kernel.org
Subject: Re: "Btrfs: device_list_add() should not update list when mounted" breaks subvol mount
Date: Thu, 11 Sep 2014 10:37:32 +0800	[thread overview]
Message-ID: <54110AEC.6040301@oracle.com> (raw)
In-Reply-To: <20140911002241.201bc6c2@datenkhaos.de>


Hi Johannes,

> I've two more systems with kernel version >3.17-rc3
> running and no problem like this.

  Does this 3.17-rc3 also has the same type of subvol config
  and it mount operation/sequence as you mentioned ?

 > - one hdd with btrfs
 > - default subvolume (rootfs) is different from subovlid=0
 > - at boot, several subvols are mounted at /home/$DIR

  I ran a few tests, on our mainline
  ----
  mount -o subvol=sv1 /dev/sdh1 /btrfs
  mount /dev/sdh1 /btrfs
   mount: /dev/sdh1 already mounted or /btrfs busy [*]
  mount /dev/sdh1 /btrfs1
  echo $?
  0
  -----

  [*] hope this isn't the problem you are mentioning.

Thanks, Anand

  parent reply	other threads:[~2014-09-11  2:33 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 [this message]
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
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=54110AEC.6040301@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=johannes.hirte@datenkhaos.de \
    --cc=linux-btrfs@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 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.