linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dexter Filmore <Dexter.Filmore@gmx.de>
To: Gordon Henderson <gordon@drogon.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Slackware and RAID
Date: Sat, 16 Sep 2006 20:39:09 +0200	[thread overview]
Message-ID: <200609162039.09488.Dexter.Filmore@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.56.0609161934270.21474@lion.drogon.net>

> > What's the remaining third?
> > 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.
>
> Have you tried simply setting the partition types to 0xFD and relying on
> the kernel auto-detect?
>
> I read here that there seems to be some resistance to this method though,
> but I've been using it for many years without any issues - however I'm not
> doing any thing "clever" like LVM or RAID on RAID (RAID1+0, etc.)

That's what I actually do: one big 0xFD partition per disk, raid5, lvm2, 3x 
xfs.
I run the array with
mdadm --assemble /dev/md0
and stop it with 
mdadm --stop --scan
after fs are unmounted and LVM is deactivated.


-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.stop1984.com
http://www.againsttcpa.com

  reply	other threads:[~2006-09-16 18:39 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 [this message]
2006-09-18 23:45     ` Bill Davidsen

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=200609162039.09488.Dexter.Filmore@gmx.de \
    --to=dexter.filmore@gmx.de \
    --cc=gordon@drogon.net \
    --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).