[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: A few crashes with yesterday's amd64-current -- IPv6 related?
On Wed, Mar 8, 2017 at 12:32 AM, Tom Ivar Helbekkmo
> Tom Ivar Helbekkmo <tih%hamartun.priv.no@localhost> writes:
>> It seems rather unwilling to crash again. It's possible, I guess,
>> that the last one was actually due to the corrupted file system, which
>> I fixed. I'll keep trying, anyway.
> It seems I didn't entirely fix it, and that was, indeed, it. I still
> haven't been able to fix it completely, but with the troublesome inode
> sitting as an empty file in /lost+found, things seem stable. I guess
> I'll have to boot from CD, and dump, newfs and restore the file system.
> (I used fsdb to fake a link count of 1 on the inode, so that fsck put it
> in lost+found. Just clearing it made the problem come back next boot.)
> Heads up to those others who've experienced fs crashes, in other words.
The issue of ffs has been fixed in PR kern/52045.
> However, with the fixes committed by ozaki-r, it seems the networking
> troubles with re devices have been solved, which is very nice. :)
Main Index |
Thread Index |