> Why writing on a file system (and not directly on /dev/sdb or whatever > the last letter) when you want to test the hardware? The file system > may always write at the same place or, in the contrary, prefer to > write on blocks that have been less used in the past (for instance, I > believe btrfs does that to lengthen SSD's lives). Here are > consequences for these two extremal writing strategies:
I think caching should also affect the results. > while true > do > if [ `cat /dev/urandom | tee $DEVICE | md5sum` = `cat $DEVICE | md5sum` ] > then > counter=`expr $counter + 1` > echo $counter successful iterations > fi > done "cat $DEVICE" might get data from before the write. Would serialize it and find a way to not cache the data.
pgpfjpE94fXJt.pgp
Description: PGP signature
