| 1 |
Ah, I nearly forgot this post! |
| 2 |
|
| 3 |
Two boards? Synchronisation mechanism? (just interested) |
| 4 |
Anyway, would be too expensive for too little gain. Not that paranoid |
| 5 |
at the moment, sorry :) |
| 6 |
|
| 7 |
Well, I already came to my conclusions about how should I do, just |
| 8 |
details is quite uncertain. |
| 9 |
Since that is not really a "hardware raid1" on my board (C7 CPU) and |
| 10 |
there are lot more issues, if controller burns, I put ideas about |
| 11 |
hardware raid away quite soon. |
| 12 |
Linux software raid? Could be, but it still holds the risk of "what |
| 13 |
happens if disk controllers write crap somehow"? (yes, yes, unlikely, |
| 14 |
but still) |
| 15 |
|
| 16 |
Since raid1 would be nearly two times slower for C7 board and I mostly |
| 17 |
do not need immediate synchronisation (plus power consumption is very |
| 18 |
limited), I figured out something interesting; at least for me: system |
| 19 |
is mostly operating single disk, but periodically synchronises* |
| 20 |
contents with second disk, that is not spinning in other times. For |
| 21 |
extra safety, it would be very good, if there was moving backup in |
| 22 |
RAM, which mirrors files matching paths in list. By "moving" I |
| 23 |
understand filling some 500MB with those important data copies and |
| 24 |
deleting oldest, that would be synchronised to second HDD, if used |
| 25 |
properly. |
| 26 |
|
| 27 |
* that should be done by maintaining changelog of filesystem since |
| 28 |
last sync for all files - any suggestions how to do that? |
| 29 |
|
| 30 |
And .. doest that seam an overkill, if I want that RAM mirror work |
| 31 |
well and "move"? |
| 32 |
|
| 33 |
Jan |
| 34 |
|
| 35 |
On 10/21/08, Geoff Swan <geoff.swan@××××××××.com> wrote: |
| 36 |
> |
| 37 |
>> Which option is safer in general, when talking about small embedded |
| 38 |
> boards: |
| 39 |
>> hardware or software raid1? |
| 40 |
> |
| 41 |
> In terms of recovering data after a crash I think software raid is |
| 42 |
> safer, or |
| 43 |
> at least easier to recover. The advantage being that the data storage on |
| 44 |
> a software |
| 45 |
> RAID1 disk looks like any other non-raid disk. Depending on the hardware |
| 46 |
> RAID controller |
| 47 |
> you may not be able to read the data on your disk without the hardware |
| 48 |
> raid controller. |
| 49 |
> |
| 50 |
> Geoff |
| 51 |
> |
| 52 |
> - I think I think, therefore I possibly am - |
| 53 |
> |
| 54 |
> |
Archives