On Wed, 15 May 2002, der Mouse wrote:

# When I tried fsck with deliberately orphaned inodes with nonzero size
# (I used clri on the containing directory), it put them in lost+found.

Well, that'll teach me not to put in what went by, but I was so
incredulous myself at having seen it that I didn't catch it all.

"Oh, for a scrollable wscons!"

It looked kind of like

UNREF FILE I=NNNN OWNER=greywolf MODE=100644 SIZE=664299 MTIME= some date
(CLEARING)

when it all went by.

Needless to say, this was not pleasant to watch my work files (recoverable!)
vapourise.

# I didn't use -p, because your original message didn't say anything
# about -p.  I'd also be interested to know whether the inodes had zero
# link count or not.  I'll try to experiment a bit (with vnd and files)
# and see if I can reproduce your symptoms with various combinations of
# options.  Certainly an initial test didn't, so I think mycroft can be
# excused the incredulity (though the way he picked to express it is
# another matter).

Well, let's just say I've learned better.  Next time I run fsck by hand
after a crash. :(

				--*greywolf;
--
NetBSD:  exercised any daemons lately?