Charles Hannum writes:

>fsirand(8) had a serious bug that would cause it to damage file
>systems larger than 4GB.  I've fixed this, and the change should show
>up in tonight's update.

1) Was this a problem in 1.2G?

2) Is it a problem with remote NFS filesystems, or only local
filesystems?

The reason I'm interested is that I have a machine running untainted
1.2G that mounts two very important 13GB filesystems via NFS. I don't
want to take the time to upgrade this system to -current unless
absolutely necessary, but don't want to whack up the 15GB or so of
stuff currently stored on these disks.