Re: panic: handle_written_inodeblock: live inodedep

> > hi,
> > i am running 5.2 release - anyone having seen such problems. i am asking
> > cause i am not sure whether it is a fbsd or a hardware problem ...
> 
> (re: subject)
> 
> I haven't had it happen to me, but someone else has.  Are your disks
> particularly full?

no they are not. disk usage is between 25% to 60% ...

> 
> I believe the report was that it happened if you performed a large I/O
> operation just after booting with a dirty filesystem, so it was running
> concurrently with bgfsck.

this could be a point - when i got that panic i had one before (hardware
compatibility problems with geforce2, via kt 133 and amd) and i booted
with a dirty fs (of course running bgfsck). 
in this situation i started portupgrade (ok possible not a good idea :)
...

> 
> It might be repeatable with a generic snapshot.

i am not sure whether i want to "repeat" it with my system - i could
cause data loss, couldnt it ?

so the advice would be to avoid havy io when running bgfsck ?? (as
workaround)

seb