All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Martin Volf <martin.volf.42@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs fi du ERROR
Date: Mon, 21 Mar 2016 08:25:04 -0400	[thread overview]
Message-ID: <56EFE820.1020407@gmail.com> (raw)
In-Reply-To: <CAM1AHpQgH=Zn_k_pHMTpYfdY_xdrOZxo=x8R=Wd7nZ3gcsVX3w@mail.gmail.com>

On 2016-03-21 02:37, Martin Volf wrote:
> Hello,
>
> I have just tried the new "btrfs fi du" command from btrfs-progs 4.5
> on 4.4.6 linux kernel, and it gave me:
>
> # btrfs fi du /bin
>       Total   Exclusive  Set shared  Filename
> (many lines of output for individual files, probably OK)
> ...
> ERROR: cannot check space of '/bin': Unknown error -1
>
> The -1 is ETXTBSY in this case:
>
> # strace -o log btrfs fi du /bin &>/dev/null; tail log
>
> newfstatat(3, "login", {st_mode=S_IFREG|0755, st_size=44784, ...}, 0) = 0
> stat("/bin/login", {st_mode=S_IFREG|0755, st_size=44784, ...}) = 0
> open("/bin/login", O_RDWR)              = -1 ETXTBSY (Text file busy)
> close(3)                                = 0
> write(2, "ERROR: ", 7)                  = 7
> write(2, "cannot check space of '/bin': Un"..., 46) = 46
> write(2, "\n", 1)                       = 1
> write(1, "     Total   Exclusive  Set shar"..., 3161) = 3161
> exit_group(1)                           = ?
> +++ exited with 1 +++
>
> Read-only snapshots give Unknown error -1 too, this time EROFS.
>
> Is it expected?
>
Thanks for reporting this, I've sent a patch to fix it.

      parent reply	other threads:[~2016-03-21 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  6:37 btrfs fi du ERROR Martin Volf
2016-03-21 11:19 ` Austin S. Hemmelgarn
2016-03-21 12:25 ` Austin S. Hemmelgarn [this message]

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=56EFE820.1020407@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin.volf.42@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.