Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [bug] error communication from kernel to userland
Date: Mon, 08 Apr 2013 11:39:56 +0800	[thread overview]
Message-ID: <51623C0C.4060709@oracle.com> (raw)


Hi,

  the below example tells a problem..

  ----
  # btrfs dev del missing /btrfs
  ERROR: error removing the device 'missing' - Invalid argument

  # dmesg | tail
  ::
  [ 4295.258686] btrfs: unable to go below two devices on raid1
  #
  -----
  as of now the more accurate errors are being logged to dmesg,
  which a normal user might not notice and there are few other
  btrfs cli cases similar to this.

  We need to get the kernel errors to the useland as part the
  cli being used.

  However the btrfs is relaying on the limited set of errno
  defines which is insufficient / inappropriate in the
  btrfs context.

  As a solution we have 2 choices broadly.. as of now

  - Update the errno with more FS and RAID related defines

  - Get the error string as part of ioctl arg.

  - ?


  any comments / questions / views / ideas are welcome..


Thanks, Anand

             reply	other threads:[~2013-04-08  3:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  3:39 Anand Jain [this message]
2013-04-26  9:39 ` device delete to get errors from the kernel Anand Jain
2013-04-26  9:41   ` [PATCH] btrfs-progs: " Anand Jain
2013-04-26  9:41     ` [PATCH] btrfs: " Anand Jain
2013-04-29 19:12       ` Josef Bacik
2013-04-30  5:55         ` Anand Jain
2013-04-26 10:51   ` Stefan Behrens
2013-04-30  6:14     ` Anand Jain
2013-04-30 13:17   ` Anand Jain
2013-04-30 13:19     ` [PATCH v2] btrfs: " Anand Jain
2013-04-30 13:19       ` [PATCH v2] btrfs-progs: " Anand Jain
2013-05-17 10:53         ` [PATCH v3] " Anand Jain
2013-05-06 19:39       ` [PATCH v2] btrfs: " Josef Bacik
2013-05-17 10:52       ` [PATCH v3] " Anand Jain

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=51623C0C.4060709@oracle.com \
    --to=anand.jain@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox