From: NeilBrown <neilb@suse.de>
To: Philipp Wendler <ml@philippwendler.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Yet another corrupt raid5
Date: Wed, 9 May 2012 06:40:01 +1000 [thread overview]
Message-ID: <20120509064001.5c937942@notabene.brown> (raw)
In-Reply-To: <4FA6428B.802@philippwendler.de>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
On Sun, 06 May 2012 11:21:15 +0200 Philipp Wendler <ml@philippwendler.de>
wrote:
> So I did it, and it worked out fine on the first try.
> Luks could successfully decrypt it, fsck did not complain, mounting
> worked and data is also fine. So hurrayy and big thanks ;-)
> Now I am running the resync.
Good news! thanks for letting us know.
>
> >> Thank you very much in advance for your help.
> >
> > Good luck, and please accept my apologies for the bug that resulted in this
> > unfortunate situation.
>
> Hey, you don't need to apologize. I am a software developer as well, and
> I know that such things might happen. And it didn't crash my data, so
> everything is fine.
>
> On the contrary, I want to thank all the developers here that you do all
> this work I can use for free (in both senses) and now when there was a
> problem, I could ask on this list and get such a extensive and helpful
> answer, although I am this "yet another guy" that asks something for the
> x-th time.
I find "Do unto other what you would have others do to you" to be a very good
idea.
And the more I can encourage people to test my development code and report
bugs, the more bugs I can fix before they get to paying customers - and that
is certainly a good thing :-)
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-05-08 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 12:42 Yet another corrupt raid5 Philipp Wendler
2012-05-06 6:00 ` NeilBrown
2012-05-06 9:21 ` Philipp Wendler
2012-05-08 20:40 ` NeilBrown [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=20120509064001.5c937942@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=ml@philippwendler.de \
/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).