From: Can Jeuleers <can.jeuleers@gmail.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Automatically adding spares on boot
Date: Sun, 20 Jan 2013 13:29:47 +0100 [thread overview]
Message-ID: <50FBE33B.8030502@gmail.com> (raw)
In-Reply-To: <33203141.4.1358684502114.JavaMail.root@zimbra>
On 01/20/2013 01:21 PM, Roy Sigurd Karlsbakk wrote:
> That's rather old too, and soon out of support. Better upgrade to 12.04 LTS and try again.
I do know that.
I reported this bug when the release on which I reported it was still
current. I didn't have this problem on 2 subsequent Ubuntu releases and
now I'm having it again on 11.10. So I did something about it myself and
I posted the solution so others can help themselves too.
prev parent reply other threads:[~2013-01-20 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:09 Automatically adding spares on boot Can Jeuleers
2013-01-19 8:23 ` Can Jeuleers
2013-01-19 18:27 ` Roy Sigurd Karlsbakk
2013-01-19 18:41 ` Can Jeuleers
2013-01-20 11:51 ` Roy Sigurd Karlsbakk
2013-01-20 12:00 ` Can Jeuleers
2013-01-20 12:21 ` Roy Sigurd Karlsbakk
2013-01-20 12:29 ` Can Jeuleers [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=50FBE33B.8030502@gmail.com \
--to=can.jeuleers@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=roy@karlsbakk.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 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).