Softupdates not preventing lengthy fsck

[Don Lewis]

On 12 Apr, Scott Long wrote:
> Kris Kennaway wrote:

>> I can take a transcript of the entire fsck next time if you like :-)
>> (it ran for more than 5 hours on the 24G drive and was still going
>> after I went to bed)
>> 
>> Kris
> 
> Don might not know that your workload involves creating and deleting
> full ports/ trees repeatedly, and those trees contain hundreds of
> tousands of inodes each.

I suspected that, especially given the inode timestamps in the partial
transcript.

> If there is a reference count leak and those
> deletions aren't ever being finalized, then there would be a whole lot
> of work for fsck to do =-)  Might also explain why disks have been
> unexpectedly filling up on package machines (like mine).

Sounds likely.  When the disk starts looking unexpectedly full, can you
unmount the file system or does the attempt fail with and EBUSY error?
What happens if you fsck the file system after it has been unmounted?
Are snapshots being used?