Re: Repeated ffs_newvnode panic (dup alloc) on one inode
Edgar Fuß <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.kernel |
|---|---|
| Message-ID | <[email protected]> |
> All seems fine, so I don't know what happened in the first place Neither do I. > and why that apparently vanished. As far as I understood, the inode was in a state where fsck and fsdb regarded it as free, but ffs choked on it. Maybe there's room for improvement in fsck.