From: Stefan Behrens <sbehrens@giantdisaster.de>
To: slp644161@pook.it
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: uncorrectable errors after btrfs replace
Date: Tue, 20 Aug 2013 16:50:08 +0200 [thread overview]
Message-ID: <52138220.90102@giantdisaster.de> (raw)
In-Reply-To: <51d7d04e-78a2-4f6c-a331-fb489c0e740f@email.android.com>
On Tue, 20 Aug 2013 15:52:27 +0200, slp644161 wrote:
> Stefan Behrens <sbehrens@giantdisaster.de> wrote:
>
>> Do you still have the kernel log files around that had been written
>> while you ran the replace procedure? /var/log/messages*. Could you
>> share
>> these files (via personal mail if the files are too huge).
>
> Yes I still have them. I'm away at the moment so I'll not be able to send them to you before Saturday. What is the maximum size that I should send to the mailing list?
>
> Stuart
The list server blocks mails larger then 100k characters according to
<http://vger.kernel.org/majordomo-info.html>.
prev parent reply other threads:[~2013-08-20 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1753593Ab3HRQvp/20130818165145Z+301@vger.kernel.org>
2013-08-18 19:12 ` uncorrectable errors after btrfs replace Stuart Pook
2013-08-18 21:43 ` Chris Murphy
2013-08-18 22:35 ` Stuart Pook
2013-08-19 0:42 ` Chris Murphy
2013-08-19 1:21 ` George Mitchell
2013-08-20 14:46 ` slp644161
2013-08-20 15:16 ` Stefan Behrens
2013-08-25 22:10 ` Stuart Pook
2013-08-26 2:07 ` Chris Murphy
2013-08-26 2:32 ` Chris Murphy
2013-09-02 16:23 ` Stefan Behrens
2013-08-20 9:44 ` Stefan Behrens
2013-08-20 13:52 ` slp644161
2013-08-20 14:50 ` Stefan Behrens [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=52138220.90102@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=slp644161@pook.it \
/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.