(04-04-2016, 10:09 AM)Andrew2 Wrote:(04-04-2016, 07:44 AM)Luke Wrote:(04-04-2016, 06:46 AM)Andrew2 Wrote:(04-04-2016, 06:40 AM)Luke Wrote: I am running a class 10 32gb Samsung card.
That's not the point. You get 'Samsung class 10 cards' that are 20 times faster than 'Samsung class 10 cards'. The most important performance factor is random I/O and not speed class or sequential transfer speeds. Therefore it's still interesting how your SD card performs in this regard.
This is as far as it gets and then crashes:
Run began: Mon Apr 4 13:38:57 2016
Include fsync in write timing
O_DIRECT feature enabled
Auto Mode
File size set to 102400 kB
Record Size 4 kB
Record Size 16 kB
Record Size 512 kB
Record Size 1024 kB
Record Size 16384 kB
Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2
Output is in kBytes/sec
Time Resolution = 0.000001 seconds.
Processor cache size set to 1024 kBytes.
Processor cache line size set to 32 bytes.
File stride size set to 17 * record size.
random random bkwd record stride
kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread
102400 4
How does the dmesg output looks like? Any indication of filesystem corruption already? I have a few faulty/counterfeit SD cards collected and these are the only ones where iozone appears to 'crash' (since a filesystem corruptions occurs and the FS will be remounted read-only)
The image did on me completely reinstalling now on a different SD card. Will rerun and retry iozone once I get it up and running...