> And it repairs the filesystem without problems. Thanks!

Damn, spoke too early. I ran it on the freshly - repaired filesystem
again, and it said:

./fsck_lfs -yf /dev/rsd1h
** /dev/rsd1h
** File system is already clean
** Last Mounted on 
** Phase 0 - Check Inode Free List
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Segment Block Accounting
segment 3005 claims 335872 bytes but has 0 (high by 335872)

fix? yes

segment 3023 claims 991232 bytes but has 983040 (high by 8192)

fix? yes

segment 4297 claims 301440 bytes but has 268672 (high by 32768)

fix? yes

segment 4394 claims 270336 bytes but has 0 (high by 270336)

fix? yes

segment 4441 claims 294912 bytes but has 253952 (high by 40960)

fix? yes

segment 4443 claims 282112 bytes but has 273920 (high by 8192)

fix? yes

segment 4542 claims 278528 bytes but has 0 (high by 278528)

fix? yes

segment 4604 claims 225280 bytes but has 0 (high by 225280)

fix? yes

segment 4605 claims 188416 bytes but has 0 (high by 188416)

fix? yes

segment 4639 claims 779648 bytes but has 771456 (high by 8192)

fix? yes

segment 4667 claims 222592 bytes but has 177536 (high by 45056)

fix? yes

segment 4709 claims 90112 bytes but has 0 (high by 90112)

fix? yes

segment 4726 claims 140288 bytes but has 0 (high by 140288)

fix? yes

segment 4737 claims 109568 bytes but has 0 (high by 109568)

fix? yes

segment 4741 claims 104448 bytes but has 0 (high by 104448)

fix? yes

segment 4744 claims 139264 bytes but has 0 (high by 139264)

fix? yes

segment 4754 claims 87040 bytes but has 0 (high by 87040)

fix? yes

segment 4756 claims 65536 bytes but has 0 (high by 65536)

fix? yes

segment 4757 claims 84992 bytes but has 0 (high by 84992)

fix? yes

segment 4758 claims 47104 bytes but has 0 (high by 47104)

fix? yes

segment 4759 claims 87040 bytes but has 0 (high by 87040)

fix? yes

segment 4761 claims 53248 bytes but has 0 (high by 53248)

fix? yes

segment 4765 claims 44032 bytes but has 0 (high by 44032)

fix? yes

segment 4766 claims 68608 bytes but has 0 (high by 68608)

fix? yes

segment 4767 claims 68608 bytes but has 0 (high by 68608)

fix? yes

segment 4769 claims 6144 bytes but has 0 (high by 6144)

fix? yes

segment 4775 claims 56320 bytes but has 0 (high by 56320)

fix? yes

segment 4785 claims 26624 bytes but has 0 (high by 26624)

fix? yes

segment 4792 claims 64512 bytes but has 0 (high by 64512)

fix? yes

segment 4798 claims 40960 bytes but has 0 (high by 40960)

fix? yes

segment 5018 claims 1040384 bytes but has 1032192 (high by 8192)

fix? yes

segment 5036 claims 1043840 bytes but has 1035648 (high by 8192)

fix? yes

segment 5047 claims 1036544 bytes but has 1020160 (high by 16384)

fix? yes

segment 5122 claims 471552 bytes but has 446976 (high by 24576)

fix? yes

segment 5123 claims 16000 bytes but has 984704 (low by 968704)

fix? yes

segment 5124 claims -23936 bytes but has 1022592 (low by 1046528)

fix? yes

segment 5125 claims 115456 bytes but has 983808 (low by 868352)

fix? yes

408192 bytes contained in 'clean' segment 5126

dirty segment? yes

avail given as 3085856, should be 3084832

fix? yes

nclean given as 3195, should be 3194

fix? yes

** Phase 6 - Roll Forward
211225 files, 3707237 used, 3310551 free

WRITE CHANGES TO DISK? yes

WRITING CHANGES TO DISK

UPDATE STANDARD SUPERBLOCK? yes


MARK FILE SYSTEM CLEAN? yes


***** FILE SYSTEM MARKED CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****