Hi Phillipp. I couldn't find a quick fix so I recommend using the
very first patch I sent you that changes the KASSERT that was
causing the panic. I am comitting a slight variation of that patch to
current now and stable in two days.
The KASSERT was being a little too conservative in regards to dirty
bits that are 'beyond the file EOF'. These get set when you dirty a
mmap'd page, but only some of them get cleared when the filesystem
buffer (containing the last fragment of a file) is synced, leaving
m->dirty looking something like 0xFC. I believe the extra page cleaning
write that occurs (and has occured for the last year) is harmless
enough for now.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
