Uggg...!!! That's not what I wanted to here....This "westporter" seller is based on my experience known to try to get every extra $ out of whatæs being ofered. From what i read here, there is a push for price up both for BO and now with "shipping".
Yeah, that's because the device isn't a block device natively, it's a memory device.You appear to not be able to view the drive write bits without the kernel module being installed.
You can read a bunch of other stuff from the device without the kernel module (temperature, voltages, etc...), I would have initially guessed lifetime stuff would use the same interface.Yeah, that's because the device isn't a block device natively, it's a memory device.
You need the kernel module to provide the virtual block layer and do the address translation.
It's kinda the opposite of how virtual memory/swap work.
1 durr@xenbox:/media/Storage/IODrive/3.2.15$ sudo fio-status -fj | grep "total_physical_bytes_\|rated_writes_remaining_percent" "rated_writes_remaining_percent" : "99.22", "total_physical_bytes_read" : "142,530,735,115,624", "total_physical_bytes_written" : "132,992,226,053,056", "rated_writes_remaining_percent" : "99.22", "total_physical_bytes_read" : "142,328,125,438,720", "total_physical_bytes_written" : "132,771,327,338,800",
The write stats are written somewhere in the FPGA. You'd need to hook up a JTAG reader/writer to really mess with any of that stuff. The fio-sure-erase utility literally wipes ALL of the flash, so that data isn't stored in there.You can read a bunch of other stuff from the device without the kernel module (temperature, voltages, etc...), I would have initially guessed lifetime stuff would use the same interface.
Are write stats actually stored on on the flash? Doesn't that mean you could fiddle with the kernel module to trivially falsify all those numbers?
The ioDrives were really never intended to be stand-alone devices. Originally, they were going to be part of a flash array, but that device was going to be much more complex to produce. As a stop-gap measure, the flash modules were attached to pci-e carrier boards (they used to be two-piece PCBs) and then sold individually. We then discovered that things like mdraid worked just fine to build arrays out of the cards and that route was chosen for larger data requirements.These things are hard core.
FWIW, it's almost certainly on a EEPROM or similar on the card. The process nodes used to manufacture big FPGAs doesn't support producing EEPROM cells. My understanding is that Xilinx's "Non Volatile" FPGAs are actually manufactured by wirebonding a separate program flash IC to the actual FPGA die, and then the whole thing is encapsulated in a single package (There was a app note about how Xilinx changed the Spartan-3 AN flash IC die mid-production, it resulted in the need to update some files so they'd program correctly).The write stats are written somewhere in the FPGA.
It'd be hard to get anywhere without a constraint file for pin definitions, at least.If you knew a lot about FPGA programming, you could probably have some fun with the cards.