From: Roman Mamedov <rm@romanrm.ru>
To: Keith Keller <kkeller@wombat.san-francisco.ca.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: vess raid stripes disappear
Date: Thu, 9 May 2013 21:10:16 +0600 [thread overview]
Message-ID: <20130509211016.718dff41@natsu> (raw)
In-Reply-To: <t7qs5axa4b.ln2@goaway.wombat.san-francisco.ca.us>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
On Thu, 09 May 2013 07:59:41 -0700
Keith Keller <kkeller@wombat.san-francisco.ca.us> wrote:
> On 2013-05-09, mashtin.bakir@gmail.com <mashtin.bakir@gmail.com> wrote:
> > I have an interesting problem with a Vessraid 1830s.
>
> Is this a hardware RAID controller? If so, you are probably looking for
> a different group. This mailing list is specific to linux md software
> RAID. You can try the comp.os.linux.misc newsgroup instead.
I (also) was under impression that linux-raid is not just for md, but for all
kinds of RAID in GNU/Linux. It's just that historically it's mostly about md.
However the poster is highly unlikely to find anyone experienced with an
obscure h/w RAID controller here (I am almost willing to bet that majority of
the readers see the name "Vess RAID" for the first time in that very post).
My advice to them would be to switch the controller into a dumb SATA HBA mode
if possible, and use the Linux Software RAID (indeed, md). Here are some
reasons why: http://linux.yyz.us/why-software-raid.html
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-05-09 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 11:29 vess raid stripes disappear mashtin.bakir
2013-05-09 14:59 ` Keith Keller
2013-05-09 15:10 ` Roman Mamedov [this message]
2013-05-09 15:32 ` Keith Keller
2013-05-09 15:41 ` Adam Goryachev
2013-05-09 16:23 ` David Brown
2013-05-09 21:33 ` Keith Keller
2013-05-09 21:27 ` NeilBrown
2013-05-10 7:55 ` SOLVED " Stan Hoeppner
2013-05-10 12:44 ` mashtin.bakir
2013-05-10 14:17 ` Stan Hoeppner
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=20130509211016.718dff41@natsu \
--to=rm@romanrm.ru \
--cc=kkeller@wombat.san-francisco.ca.us \
--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).