I am not subscribed to linaro-dev, so please Cc me in case you drop flashbench-results
mailinglist from receivers.
Hi Arnd, hi everyone!
For now quick and short.
A simple script to automate common steps on reporting flash medium test
results. It goes as far as read tests for erase block size and then suggests
some open au tests together with a warning that these write to the device.
I checked other flashbench-results posts as to what info would be
interesting.
Find it at:
git://gitorious.org/flashbench/flashbench.git
Example output is at:
[Flashbench] Samsung Plus MB-SPAGFFP Class 10 SDHC 16GB
Sat Dec 1 16:02:18 UTC 2012
http://lists.linaro.org/pipermail/flashbench-results/2012-December/000346.h…
Sorry that I occupied flashbench upstream name for project. I can look
into renaming it to "flashbench-martin" or something like that.
The script is in branch "flashreport".
In branch "defaultblocksize" you find a currently untested patch for
changing default block size to 1024.
I can try to send patches as mails via git, but I´d have to look it up first,
since I do this quite rarely.
Up to then please use the repo urls :)
Nice weekend,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Salut,
for housing a debian chroot in my android phone, I want to set up a 2.5G
partition on this new micro sd card. For that, I want to figure out
which parameters to give to mke2fs, as in
> mkfs.ext4 -E stride=2,stripe-width=2048 -L debian_chroot /dev/sdb2
Now to figure out the internal erase block size, flashbench was
recommended. But I can not quite make sense of my result..
> # fdisk.distrib -l /dev/sdb
>
> Disk /dev/sdb: 15.9 GB, 15931539456 bytes
> 255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000604f9
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 2048 25890815 12944384 b W95 FAT32
> /dev/sdb2 25890816 31115263 2612224 83 Linux
> # flashbench -va /dev/sdb --blocksize=1024 |(echo "align,pre [µs],on [µs],post [µs],diff [µs]" && sed -r 's/\w+ //g;s/\t/,/g;s/[0-9]+ns*/0/g;s/µs//g')|tee flashbench-16gb-sandisk-extreme-microsdhc-blocksize-1024.csv
> # flashbench -va /dev/sdb --blocksize=$[3*1024] |(echo "align,pre [µs],on [µs],post [µs],diff [µs]" && sed -r 's/\w+ //g;s/\t/,/g;s/[0-9]+ns*/0/g;s/µs//g')|tee flashbench-16gb-sandisk-extreme-microsdhc-blocksize-$[3*1024].csv
resulting CSV files attached.. I created a spreadsheet chart showing a
drop.. does this mean the erasure block size is 128KB?
That would give a stripe-width of 128KB/(2*4KB)=16?
And I have not at all grokked the benefit/applicability of
open-au/open-au-nr for practical purposes..
Any clarification greatly appreciated.
#Regards!Marcel
