Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Roger Binns <rogerb@rogerbinns.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs device ready non-success exit code
Date: Fri, 05 Jun 2015 07:25:24 +0800	[thread overview]
Message-ID: <5570DE64.5020104@oracle.com> (raw)
In-Reply-To: <mkq3i4$r5d$1@ger.gmane.org>



On 06/05/2015 01:57 AM, Roger Binns wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> This is on current Ubuntu 15.04.  What is device ready unhappy with?
> Note that the root filesystem and /home (both subvolumes of this) are
> mounted and working perfectly, and even where the commands are run from.
>
> $ sudo btrfs fi show /dev/sda1
> Label: 'main'  uuid: 3ff68715-0daa-4e44-8de2-0997f36d8ab6
> 	Total devices 2 FS bytes used 417.22GiB
> 	devid    2 size 894.25GiB used 362.03GiB path /dev/sdb1
> 	devid    3 size 894.25GiB used 362.03GiB path /dev/sda1
>
> Btrfs v3.17
> $ sudo btrfs fi show /
> Label: 'main'  uuid: 3ff68715-0daa-4e44-8de2-0997f36d8ab6
> 	Total devices 2 FS bytes used 417.22GiB
> 	devid    2 size 894.25GiB used 362.03GiB path /dev/sdb1
> 	devid    3 size 894.25GiB used 362.03GiB path /dev/sda1
>
> Btrfs v3.17
> $ sudo btrfs device ready /dev/sda1 ; echo $?
> 1
> $ sudo btrfs device ready /dev/sdb1 ; echo $?
> 1


typically ready cli is to check disk pool status in an unmounted state.

Strictly we wanted ready cli to be a read only cli, but it updates the 
device path as well, which eventually I think we will fix it, if the
systemd won't compliant about it.

-Anand


> $ uname -a
> Linux workstation 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> Roger
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iEYEARECAAYFAlVwkX4ACgkQmOOfHg372QTEjQCgmhFU8Gxx8VOeNay2fkJjgpaU
> ZOEAn18pogQVQnS8AzPzSEY7gu6rH+q3
> =foM6
> -----END PGP SIGNATURE-----
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2015-06-04 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 17:57 btrfs device ready non-success exit code Roger Binns
2015-06-04 23:25 ` Anand Jain [this message]
2015-06-05  3:04   ` Roger Binns

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=5570DE64.5020104@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rogerb@rogerbinns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox