Whelp, that's bizarre: AFAICT that file type has never been used by any of
the mainline BSDs.
I guess you could have had a bitflip from a bug (or drive issue, or cosmic
ray, etc) and it should really be either 0120000 (symlink) or 0140000
(socket). You could try tracking it down (update dump to print the inum
too?) and then use find(1) to see what path(s) it has to get a hint about
what it should have been, and then maybe use fsdb to change its type to
what seems the correct one, though I would *test* my backup before doing
that and be prepared to spend the time to newfs+restore the filesystem in
case things go wrong.
Philip
On Fri, Sep 22, 2023 at 12:44 PM vitmau...@gmail.com <vitmau...@gmail.com>
wrote:
> Dear Philip,
>
> thank you for pulling my ears. The complete error message is:
>
> DUMP: Warning: undefined file type 0130000
>
> Best,
> Vitor
>
> Em sex., 22 de set. de 2023 às 16:17, Philip Guenther <guent...@gmail.com>
> escreveu:
>
>> On Fri, Sep 22, 2023 at 11:18 AM vitmau...@gmail.com <vitmau...@gmail.com>
>> wrote:
>>
>>> I'm also getting an "undefined file type" error from dump. I found one
>>> guy
>>> from the FreeBSD mail list that got the same error, but he solved his
>>> problem using fsck on the partition. I forced fsck on my side, since the
>>> filesystem was marked as clean, but to no avail.
>>>
>>
>> In OpenBSD's dump, that warning includes the actual file type which
>> provoked the error:
>>
>> : bleys; pwd
>> /usr/src/sbin/dump
>> : bleys; grep 'undefined file type' *.c
>> traverse.c: msg("Warning: undefined file type 0%o\n",
>> : bleys;
>>
>> Since yours didn't include that, you would appear to be running some
>> other version of dump, which would make this the wrong place to get help.
>>
>> ...unless you truncated an error message before asking about it, which is
>> kinda self-defeating.
>>
>>
>> Philip Guenther
>>
>>
