linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathias Mueller <raidfail@gmx.de>
To: Phil Turmel <philip@turmel.org>
Cc: Linux raid <linux-raid@vger.kernel.org>,
	linux-raid-owner@vger.kernel.org
Subject: Re: broken raid level 5 array caused by user error
Date: Mon, 25 Jan 2016 11:02:24 +0100	[thread overview]
Message-ID: <a3edd29eacd064759b81a733ba6ecdca@pingofdeath.de> (raw)
In-Reply-To: <56A27F5E.1000602@turmel.org>

Hi Phil,

thanks a lot once more, I would never managed it without your help. It's 
very nice, that you spend so much time in supporting everyone and 
writing very helpful tools. I learned a lot, technically and also to 
have more patience and thinking twice _before_ doing things :)

> Sadly, it's hard to ship beer here in the US without government 
> involvement.

That's a very sad fact! I send you something via paypal, so you might 
get some german beer from some US store, if you like. Tell me, if you 
need consulting ;)

Keep on going and best regards

Mathias

  reply	other threads:[~2016-01-25 10:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 21:33 broken raid level 5 array caused by user error Mathias Mueller
2015-11-10 21:41 ` Phil Turmel
2015-11-10 23:47   ` Mathias Mueller
2015-11-10 23:59     ` Phil Turmel
     [not found]       ` <b0cdddd4394bbc1356980bb61ac199c3@pingofdeath.de>
2015-11-11  1:00         ` Phil Turmel
2015-11-11 17:53           ` Mathias Mueller
2016-01-18 15:33             ` Mathias Mueller
2016-01-18 19:09               ` Phil Turmel
2016-01-19 14:35                 ` Mathias Mueller
2016-01-19 17:51                   ` Phil Turmel
2016-01-19 19:37                     ` Phil Turmel
2016-01-20  9:04                       ` Mathias Mueller
2016-01-22  9:30                         ` Mathias Mueller
2016-01-22 17:16                           ` Phil Turmel
2016-01-22 17:39                             ` Mathias Mueller
2016-01-22 19:13                               ` Phil Turmel
2016-01-25 10:02                                 ` Mathias Mueller [this message]
2015-11-11  1:03       ` Phil Turmel
2015-11-11  1:29         ` Mathias Mueller
  -- strict thread matches above, loose matches on Subject: below --
2015-11-09 11:27 Mathias Mueller
2015-11-09 11:56 ` Mikael Abrahamsson
2015-11-09 13:50   ` Phil Turmel
     [not found]     ` <07de4cd96f39ecb6154794d072ca12e7@pingofdeath.de>
     [not found]       ` <5640B8AD.3030800@turmel.org>
2015-11-09 15:41         ` Mathias Mueller
     [not found]           ` <d764bf541381927fa4183c9266fb3f5a@pingofdeath.de>
     [not found]             ` <5640C38B.4060503@turmel.org>
     [not found]               ` <a3a91665c4b7cdd70dacc7d8815cc365@pingofdeath.de>
2015-11-09 21:13                 ` Phil Turmel
2015-11-10  8:37                   ` Mathias Mueller
2015-11-10 13:55                     ` Phil Turmel
2015-11-10 14:55                       ` Mathias Mueller
2015-11-10 15:20                       ` Mathias Mueller
2015-11-10 15:28                         ` Phil Turmel
2015-11-10 21:02                           ` Mathias Mueller
2015-11-10 21:11                             ` Phil Turmel

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=a3edd29eacd064759b81a733ba6ecdca@pingofdeath.de \
    --to=raidfail@gmx.de \
    --cc=linux-raid-owner@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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).