[Date Prev][Date Next]
bonnie and MFS don't like each other
Running bonnie on a MFS filesystem will lock up my 3.1-Stable
system everytime if the size is larger than the amount of RAM
available. (bonnie works fine otherwise).
# cd /tmp (MFS filesystem)
# bonnie -s 192 (system has 128MB ram, MFS has ~465MB avail)
Basically, bonnie tries hard to bench the MFS filesystem.
The disk goes crazy swapping, but eventually the disk activity
stops with everything else. No console messages, no response
to console input (a tty), and then, after watching a stupid movie
on TV, I pushed reset.
Note, if I run bonnie with a -s 10 or 100, it runs fine:
Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU
MFS-10 10 14211 80.3 35932 71.0 28897 76.0 17938 99.9 77781 99.9 9287.2 197.4
MFS-100 100 14158 84.5 23113 44.9 18733 51.6 13724 79.9 31208 47.3 3445.8 138.2
System runs 2 March 1999 RELENG_3 sources and is configured
for SMP (dual PII). Bonnie installed from ports on 3 March.
/dev/da0s1a on / (local, soft-updates, writes: sync 5 async 1281)
procfs on /proc (local)
mfs:24 on /tmp (asynchronous, local, nodev, nosuid, writes: sync 2 async 57)
/dev/da0s1f on /usr (local, noatime, soft-updates, writes: sync 2 async 14)
/dev/da0s1e on /var (local, noatime, soft-updates, writes: sync 99 async 753)
/dev/da0s1g on /data (local, soft-updates, writes: sync 5 async 599)
/dev/da0s1h on /work (local, noatime, soft-updates, writes: sync 2 async 0)
I would be happy to provide additional information to anyone interested
in exploring this issue.