On 10/24/14 21:51, Martin K. Petersen wrote:
"Michael" == Michael L Semon writes:
Michael> There was nothing regarding integrity in /sys/block/sda. I was
Michael> under the impression that both bio integrity and T10 checksums
Michael> require hardware support from good hardware, so the config
> "Michael" == Michael L Semon writes:
Michael> There was nothing regarding integrity in /sys/block/sda. I was
Michael> under the impression that both bio integrity and T10 checksums
Michael> require hardware support from good hardware, so the config
Michael> items have always been shut off.
On 10/24/14 15:54, Martin K. Petersen wrote:
"Michael" == Michael L Semon writes:
Michael> This week, a simple `dc3dd wipe=/dev/sda5` operation had speeds
Michael> cut from 10-15 MB/s down to less than 1.8 MB/s. With this
Michael> method, syncs took so long that magic SysRq keys were needed t
> "Michael" == Michael L Semon writes:
Michael> This week, a simple `dc3dd wipe=/dev/sda5` operation had speeds
Michael> cut from 10-15 MB/s down to less than 1.8 MB/s. With this
Michael> method, syncs took so long that magic SysRq keys were needed to
Michael> stop the PC. A bisect let me h
> "Michael" == Michael L Semon writes:
Michael> This week, a simple `dc3dd wipe=/dev/sda5` operation had speeds
Michael> cut from 10-15 MB/s down to less than 1.8 MB/s. With this
Michael> method, syncs took so long that magic SysRq keys were needed to
Michael> stop the PC.
Please send me t
Hi! I have an old i686 Pentium 4 that I use for xfstests. To better keep
integrity, write cache is disabled on an old 60-"megabyte" IDE HDD. The
PC runs slackware-current, doing a `git pull` of the kernel and
xfs-oss/for-next once or twice a week.
This week, a simple `dc3dd wipe=/dev/sda5` ope
6 matches
Mail list logo
