From: Roman Mamedov <rm@romanrm.net>
To: Simon Waid <simon_waid@gmx.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: RAID5: btrfs rescue chunk-recover segfaults.
Date: Mon, 23 Jan 2017 18:34:26 +0500 [thread overview]
Message-ID: <20170123183426.77162b6f@natsu> (raw)
In-Reply-To: <55a30f16-3793-ebac-68a5-d377b023a91e@gmx.net>
On Mon, 23 Jan 2017 14:15:55 +0100
Simon Waid <simon_waid@gmx.net> wrote:
> I have a btrfs raid5 array that has become unmountable.
That's the third time you send this today. Will you keep resending every few
hours until you get a reply? That's not how mailing lists work.
--
With respect,
Roman
next prev parent reply other threads:[~2017-01-23 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 13:15 RAID5: btrfs rescue chunk-recover segfaults Simon Waid
2017-01-23 13:34 ` Roman Mamedov [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 8:57 Simon Waid
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=20170123183426.77162b6f@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=simon_waid@gmx.net \
/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.