From: Bill Davidsen <davidsen@tmr.com>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Slackware and RAID
Date: Mon, 18 Sep 2006 19:45:03 -0400 [thread overview]
Message-ID: <450F2F7F.6090108@tmr.com> (raw)
In-Reply-To: <200609162032.07509.Dexter.Filmore@gmx.de>
Dexter Filmore wrote:
>Am Samstag, 16. September 2006 19:26 schrieb Bill Davidsen:
>
>
>>Dexter Filmore wrote:
>>
>>
>>>Is anyone here who runs a soft raid on Slackware?
>>>Out of the box there are no raid scripts, the ones I made myself seem a
>>>little rawish, barely more than mdadm --assemble/--stop.
>>>
>>>
>>I'm pretty much off Slack now, but I have run, the scripts you describe
>>are about 2/3 of what you need, see the thread(s) here about monitoring.
>>mdadm doesn't need a lot of direction...
>>
>>
>
>What's the remaining third?
>
>
Monitoring... where I pointed you.
>I fumbled it into rc.S and rc.6, reason why I ask is that array degraded about
>6 times in the few months I run it and I can't figure why. Only thing I know
>is that it degrades somewhere in the reboot process, so I suspect it might
>not properly shutdown.
>
Since I haven't had problems I'll pass on trying to guess what's
happening. When I have any problem usually a whole drive hits the floor,
and I know what to fix and how. I assume you look at mdstat after boot?
If it's clean before you shut down and dirty on boot, something isn't
shutting down clean, OR that autodetect stuff isn't working as you want
it to. I do NOT run lvm, I avoid stuff like that unless I really need it.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2006-09-18 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 10:30 Slackware and RAID Dexter Filmore
2006-09-16 17:26 ` Bill Davidsen
2006-09-16 18:32 ` Dexter Filmore
2006-09-16 18:35 ` Gordon Henderson
2006-09-16 18:39 ` Dexter Filmore
2006-09-18 23:45 ` Bill Davidsen [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=450F2F7F.6090108@tmr.com \
--to=davidsen@tmr.com \
--cc=Dexter.Filmore@gmx.de \
--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).