From: Anthony Johnson <anthony@storix.com>
To: linux-raid@vger.kernel.org
Subject: linux mkraid: segmentation fault
Date: Sun, 19 May 2002 23:17:22 -0700 [thread overview]
Message-ID: <3CE894F2.B802D66F@storix.com> (raw)
One other thing I forgot to mention. My raid tools are at 0.90-23. I
can't really update to the latest to try it again since I need to be
able to support back-level versions. Plus, the problem only happens when
I boot from my recovery media, so I'm certain it's something missing
there....Thanks.
------------
Hi,
Can you please help me or provide me a contact where I can get some
support for software raid?
My company is developing a system recovery product that creates software
raid devices, and I get a segmentation fault when I run:
mkraid -c /etc/raidtab --really-force /dev/md0
This problem doesn't occur on a normal running system, only after I have
booted from my recovery diskettes, and it occurs no matter what I have
configured in the raidtab file. I'm sure there is a problem due to
something missing from the RAM filesystem created by the recovery
diskettes but I can't find what it is.
I have rebuilt the partition map (containing md0 devices), made the
device nodes, updated the raidtab file correctly but nothing matters.
The boot media contains the necessary commands and any libraries
required (by running ldd on each executable).
Can you tell me what files or device nodes are required to make a raid
device that I might be missing? This is quite urgent as we'll be
releasing this product in only a month and we won't be able to support
systems using software raid until I resolve this.
Thanks!
Anthony
next reply other threads:[~2002-05-20 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 6:17 Anthony Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 6:14 linux mkraid: segmentation fault Anthony Johnson
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=3CE894F2.B802D66F@storix.com \
--to=anthony@storix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.