linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: office@ninti.com.au
Cc: RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: fd filesystem and RAID1
Date: Tue, 06 Apr 2004 00:48:46 +1000	[thread overview]
Message-ID: <87fzbimqep.fsf@enki.rimspace.net> (raw)
In-Reply-To: <1081156121.2301.55.camel@localhost> (Ninti Systems's message of "05 Apr 2004 18:38:41 +0930")

On 05 Apr 2004, Ninti Systems wrote:
>> > 
>> > The kernel auto-discovery will only probe a partition that has type
>> > 'fd', so if you want both parts of the mirror to work, both need to
>> > be type 'fd'.
> 
> I tried doing this to partitions on both IDE devices pre-install
> (Slackware saw them all as md devices, install impossible), and I also
> tried changing the original install disk's partitions over to 'fd'
> type after copying their content to the md device (the second disk
> also all 'fd' type).
> 
> But whatever I do the arrays never have usable superblocks, are always
> degraded and always want to resync on boot.

Hrm.  I am sorry that things have proved to be such a challenge.  One
thing to note, of course, is that a software RAID root file system is
much harder to use than any other partition done as software RAID.

You may have better luck by creating a couple of small partitions and
working with those as an "extra" drive, until you resolve the problems.

One final note:  I found the 'mdadm' tool a *vast* improvement over the
traditional RAID tools for Linux.  

> Thanks for all your help, but I'm starting to get over this RAID on
> Slackware thing. I think I'll reconsider my distro (RedHat) or my
> backup strategy (rsync).

RedHat certainly seems to offer good graphical tools for managing this
sort of thing, which can be very useful while you learn how things work.

There is nothing wrong with using a helping hand in software rather than
by email. :)

Good luck.
     Daniel

-- 
All that you suspect about women's friendships is true. We talk about dick size.
        -- Cynthia Heimel

      reply	other threads:[~2004-04-05 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 23:32 fd filesystem and RAID1 Ninti Systems
2004-04-05  0:58 ` Daniel Pittman
2004-04-05  8:00   ` Ninti Systems
2004-04-05  9:08     ` Ninti Systems
2004-04-05 14:48       ` Daniel Pittman [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=87fzbimqep.fsf@enki.rimspace.net \
    --to=daniel@rimspace.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=office@ninti.com.au \
    /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).