P.S.
On 11/19/2014 01:47 PM, Phillip Susi wrote:
Another common cause is having a dedicated hardware RAID
controller (dell likes to put LSI MegaRaid controllers in their
boxes for example), many mother boards have hardware RAID support
available through the bios, etc, leaving that feature active, then
the adding a drive and
That would be fake raid, not hardware raid.
The LSI MegaRaid controller people would _love_ to hear more about your
insight into how their battery-backed multi-drive RAID controller is
"fake". You should go work for them. Try the "contact us" link at the
bottom of this page. I'm sure they are waiting for your insight with
baited breath!
http://www.lsi.com/products/raid-controllers/pages/megaraid-sas-9260-8i.aspx
_not_ initializing that drive with the RAID controller disk setup.
In this case the controller is going to repeatedly probe the drive
for its proprietary controller signature blocks (and reset the
drive after each attempt) and then finally fall back to raw block
pass-through. This can take a long time (thirty seconds to a
minute).
No, no, and no. If it reads the drive and does not find its metadata,
it falls back to pass through. The actual read takes only
milliseconds, though it may have to wait a few seconds for the drive
to spin up. There is no reason it would keep retrying after a
successful read.
Odd, my MegaRaid controller takes about fifteen seconds by-the-clock to
initialize and to the integrity check on my single initialized drive.
It's amazing that with a fail and retry it would be _faster_...
It's like you know _everything_...
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
