> > My concern with using it to accelerate non-volatile > storage > > is partly with the prospects for human error > (adapter cord > > to trip over, command that needs to be run), but > also > > The DDRdrive X1 ACDC power cord exits the rear of the > chassis just > as the host power supply cord, if a customer has > issues with power > cords being randomly removed, the root cause needs to > be addressed > and would not be unique to the X1. We have not found > this to be an > issue.
Ok. One of the design choices that to my personal way of thinking makes documenting correct and safe use critical; more on that later. (I'm a system admin (who does _not_ work for Sun!), and concern for the worst-case in terms of human error strongly affects my perspective.) > > that in my rather cursory visit to the vendor's web > site, > > I saw no mention of ECC memory. I sure hope I just > missed > > that. > > ECC is implemented in the redundant storage area (as > stated on our website). > The redundant area is set aside because of both the > ECC and the > intrinsic NAND capacity required for bad block > replacement and is the basis > for the less than 4GB usable drive capacity. Thank you; I did see the mention of the redundant area, but didn't understand from what I saw that it served both purposes. > > Do we know if the device needs the OS to stick > around after the > > copy-to-flash command is issued? > > [A SLOG is best implemented without the added > complexities of backup/restore.] > > To answer your question, the backup/restore feature > is completely > independent of the host machine and OS and can > successfully complete > without either. LEDs (red=backup/yellow=restore) are > clearly visible on the > X1 so that progress can be tracked, e.g. backup is > initiated just prior > to system shutdown with the intention of card removal > at completion. Again, thank you; that's good to know. The indicator light seems to me to be part of what could make safe and responsible use possible. >From my system admin perspective, successful use given a minimalist design (no auto-copy to flash on loss of bus power, among other choices) is critically dependent on end-user documentation describing not only the features of the product, but their correct use as applied to supported platforms, with appropriate examples (zfs or other software volume management acceleration, database acceleration, etc). -- This message posted from opensolaris.org
