From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Crush on btrfs device delete missing
Date: Sun, 28 Aug 2016 08:06:47 +0000 (UTC) [thread overview]
Message-ID: <pan$74431$bc836653$60152c18$c71d2df3@cox.net> (raw)
In-Reply-To: 20160828142252.0ded31f7@rose
MASAKI Yuhsuke posted on Sun, 28 Aug 2016 14:22:52 +0900 as excerpted:
> btrfs device delete missing always crushes and stop system.
> It log console only not STDOUT/STDERR or core file.
While I'm unlikely to be able to help with the problem, for those who
can, you're missing some critical information, including kernel and btrfs-
progs versions (if they're old, please try a current 4.6 or 4.7 kernel if
on current, or 4.4 if on LTS, and an appropriately matched or newer btrfs
userspace as well), and btrfs filesystem usage or btrfs filesystem show
and btrfs filesystem df outputs.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-08-28 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 5:22 Crush on btrfs device delete missing MASAKI Yuhsuke
2016-08-28 8:06 ` Duncan [this message]
2016-08-28 8:41 ` MASAKI Yuhsuke
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='pan$74431$bc836653$60152c18$c71d2df3@cox.net' \
--to=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).