Well since I was bored and had nothing better to do I started writing "swraid.device" on the weekend and I have now gotten it to the point where it (hopefully) should compile and work (to some extent at least) once I get my A1 working again.
At this point I have only implemented mirroring. I think I will leave striping until I can at least test that the current code works correctly.
I'm using the diskimage.device source code as basis for this project which is why it's going so fast.
Also at some point I will have to write a prefs program of some kind (using ReAction of course).
Maybe I can test it for you, I have 3 or 4 disks here collecting dust.
Bye, TMTisFree
"Never ascribe to malice that which is adequately explained by incompetence." (Napol?on Bonaparte) "I would love to change the world, but they won?t give me the source code." (Unknown)
@salass00 I wouldn't mind a working version of this. I am intending (I have had the drive for about 6 months) to add a second hard drive just to use as a backup.
Thanks for the offer. I will likely take you up on it but first I need to get the .device compiled.
I'm using application.library's "prefsobjects" interface for the device preferences which should mean that until the proper RAID prefs program has been written it should be possible to use the PrefsObjectEditor to create the prefs file.
Also some knowledge about writing mountlists (i.e. DOSDrivers) will be needed.
As an update i did write code for striped reads and writes yesterday.
Ok. I have a SiL3112 and a SiL 3114 in the A1 atm, so I can test different configs if needed.
Bye, TMTisFree
"Never ascribe to malice that which is adequately explained by incompetence." (Napol?on Bonaparte) "I would love to change the world, but they won?t give me the source code." (Unknown)
I have a SiL3112 and a SiL 3114 in the A1 atm, so I can test different configs if needed.
Contact GuruMeditation for beta-testing if you didn't already.
The 'RAID' DOSType is just there because I forgot to remove it from the diskcache.library versions included in AmigaOS4 final and the AmiNet SFS archives, sorry. It was only supposed to be in beta versions for testing software RAID (currently 0, 1 and 5).
There is no AmigaOS4 driver for hardware RAID controllers, the sii0680, sii3114, etc. are not hardware RAID controllers, it's just a software RAID implementation their, on the AmigaOne unused, BIOS supports as well as the included windows drivers.
I have a SiL3112 and a SiL 3114 in the A1 atm, so I can test different configs if needed.
Contact GuruMeditation for beta-testing if you didn't already.
Beta-testing for what? I'm sorry but I'm surely missing something here...
Quote:
The 'RAID' DOSType is just there because I forgot to remove it from the diskcache.library versions included in AmigaOS4 final and the AmiNet SFS archives, sorry. It was only supposed to be in beta versions for testing software RAID (currently 0, 1 and 5).
Sound interesting.
Quote:
There is no AmigaOS4 driver for hardware RAID controllers, the sii0680, sii3114, etc. are not hardware RAID controllers, it's just a software RAID implementation their, on the AmigaOne unused, BIOS supports as well as the included windows drivers.
I know. The SiL 3114 I have is not even software RAID enabled.
Bye, TMTisFree
"Never ascribe to malice that which is adequately explained by incompetence." (Napol?on Bonaparte) "I would love to change the world, but they won?t give me the source code." (Unknown)
"Never ascribe to malice that which is adequately explained by incompetence." (Napol?on Bonaparte) "I would love to change the world, but they won?t give me the source code." (Unknown)
Btw, atm I use MirrorCopy as a kind-of RAID 1 mirror system, with Docket to manage some ARexx scripts to do the sync.
Bye, TMTisFree
"Never ascribe to malice that which is adequately explained by incompetence." (Napol?on Bonaparte) "I would love to change the world, but they won?t give me the source code." (Unknown)
FWIW I uploaded a v52.1 alpha version of swraid.device to OS4Depot. If you or anyone else does try it out then please do report back to me how it works (either here or by e-mail).
It may contain bugs so I wouldn't recommend to use it for storing any important data right now. I have fixed a memory leak in libOpen() for v52.2 (some device structures aren't freed if there is a failure to open the unit).