SCIENTIFIC-LINUX-USERS Archives

April 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Tue, 14 Apr 2015 11:06:18 -0700
Content-Disposition:
inline
Reply-To:
Konstantin Olchanski <[log in to unmask]>
Subject:
From:
Konstantin Olchanski <[log in to unmask]>
Content-Type:
text/plain; charset="us-ascii"
In-Reply-To:
MIME-Version:
1.0
Comments:
To: Vladimir Mosgalin <[log in to unmask]> cc: [log in to unmask]
Parts/Attachments:
text/plain (23 lines)
On Tue, Apr 14, 2015 at 06:39:52PM +0300, Vladimir Mosgalin wrote:
> 
> > Considering that the RAID technology is old which was designed for
> > rotating media, maybe that isn't the the best solution for SSD?
>

With SSD, there is still possibility of single-disk failure (SSD bricks itself).

When this happens, to protect against data loss you have 2 choices:

a) daily (hourly) rsync of SSD to some other storage (on SSD failure, machine will die, require manual recovery)
b) RAID1 with another SSD (or HDD, use "--write-mostly") (on SSD failure, machine will continue running)

SL7 comes with btrfs, which is intended to be "better RAID1" (I am presently testing this).

But SL7 cannot boot from btrfs, so you still need a /boot partition and RAID1 to protect it against single-disk failure.

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada

ATOM RSS1 RSS2