From: Rikard Morssing <rimo.nospam@vtfl.nu>
To: linux-raid@vger.kernel.org
Subject: raidreconf feedback help
Date: Wed, 6 Nov 2002 13:12:22 +0100 [thread overview]
Message-ID: <20021106121222.GA23946@vtfl.nu> (raw)
I just decided to risk it and expand my raid5-set with raidreconf. It
failed miserably (but that might be due to hw).
But it made me think. How should we create meaningful, extensive and
informative debug reports which is crucial for the developers to debug
the program? What i think should be on the raidreconf webpage is a list
of steps to perform BEFORE and AFTER running the raidreconf, and where
to send the report.
good idea?
regards
Rikard M
next reply other threads:[~2002-11-06 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 12:12 Rikard Morssing [this message]
2002-11-07 23:46 ` raidreconf feedback help (CFM!) Jakob Oestergaard
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=20021106121222.GA23946@vtfl.nu \
--to=rimo.nospam@vtfl.nu \
--cc=linux-raid@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).