Still waiting for my 830 to be delivered.Someone provided data on an 830 used in a production environment, which can be compared to the output from Christopher’s drive. (The 1st table is Christopher’s drive; the 2nd is the production drive)
Uploaded to ImageShack on account of XS not allowing you to upload imagesImageShack.us
I’ve been hassling Samsumg for info on the 177 value. What they have stated in item 2 & 3 below does not make sense and I don’t think I will get any further clarification.
1) Attribute 177 can update while the unit is on
2) The raw value on this attribute is how many time it can prolong the life of a specific block
3) The indicator range from a wider range of numbers as 1-100 is not enough.
Data from the second table seems to show that 177 can update without a power off. Maybe that is due to the different workload or maybe it just a configuration quirk on Christophers set up. Let’s see what happenes with my drive.
I still can’t be sure that 177 is the MWI, but for the purpose of the endurance test I’m going to assume it is. When it gets to 1 I will stop the test, disconnect the power and leave it for 3 months. I’m going to run a few trace benchmarks and then I will let the standard endurance test run for a day or so. I will then ramp things up with the 4K random workload.



Someone provided data on an 830 used in a production environment, which can be compared to the output from Christopher’s drive. (The 1st table is Christopher’s drive; the 2nd is the production drive)
Reply With Quote


Bookmarks