./sysutils/disk-filltest, Detect Bad Disks by Filling with Random Data

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 0.7.1, Package name: disk-filltest-0.7.1, Maintainer: pkgsrc-users

The function of disk-filltest is simple:

* Write files random-######## to the current directory until the disk is full
* Read the files again and verify the pseudo-random sequence written
* Any write or read error will be reported, either by the operating
system or by checking the pseudo-random sequence
* Optionally, delete the random files after a successful run


Master sites:

SHA1: be35c8b89410290eecc7cf547bcd59f9da71e05b
RMD160: ddcd3478ec752c8328b5e1e510f6f4022e01fa25
Filesize: 14.096 KB

Version history: (Expand)


CVS history: (Expand)


   2015-11-04 02:32:42 by Alistair G. Crooks | Files touched by this commit (499)
Log message:
Add SHA512 digests for distfiles for sysutils category

Problems found with existing digests:
	Package memconf distfile memconf-2.16/memconf.gz
	b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
	95748686a5ad8144232f4d4abc9bf052721a196f [calculated]

Problems found locating distfiles:
	Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
	Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
	Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
	Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
	Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2014-06-01 00:04:35 by David Brownlee | Files touched by this commit (4) | Imported package
Log message:
Added sysutils/disk-filltest version 0.7.1

The function of disk-filltest is simple:

* Write files random-######## to the current directory until the disk is full
* Read the files again and verify the pseudo-random sequence written
* Any write or read error will be reported, either by the operating
  system or by checking the pseudo-random sequence
* Optionally, delete the random files after a successful run