From: Lutz Vieweg <lvml@5t9.de>
To: linux-btrfs@vger.kernel.org
Subject: btrfs filesystem defrag fails with "Resource temporarily unavailable" when strace'd
Date: Fri, 26 Jun 2015 19:00:27 +0200 [thread overview]
Message-ID: <mmk0fb$jpn$1@ger.gmane.org> (raw)
I started...
btrfs filesystem defragment -v /some/directory
and this took (unexpectedly, for just 150M of data) a long time (minutes).
So I wondered whether I could see via "strace -p PID" what was going on with the process.
Immediately when strace tries to attach, the btrfs process dies with this error message:
> ERROR: defrag failed on /some/directory - Resource temporarily unavailable
This is 100% reproducable.
The strace output looks like this:
> Process 1402 attached
> brk(0) = 0x1468000
> brk(0) = 0x1468000
> brk(0x1460000) = 0x1460000
> brk(0) = 0x1460000
> close(3) = 0
> write(2, "ERROR: defrag failed on /some/d"..., 84) = 84
> write(1, "btrfs-progs v4.1\n", 17) = 17
> write(2, "total 1 failures\n", 17) = 17
> exit_group(1) = ?
> +++ exited with 1 +++
This is the first time I see a prozess crash upon strace being attached -
is this intended behaviour? If so... why?
(Tried again without strace, "the btrfs filesystem defragment" command later
finished ok, albeight after a loong time.)
Regards,
Lutz Vieweg
reply other threads:[~2015-06-26 17:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='mmk0fb$jpn$1@ger.gmane.org' \
--to=lvml@5t9.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox