The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <>
To: Lars Brinkhoff <>
Cc: The Eunuchs Hysterical Society <>
Subject: [TUHS] Re: Extracting files from various old dump/restore tapes
Date: Mon, 22 Aug 2022 10:27:31 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]

FreeBSD deleted some compat code in the kernel some time ago, and it turns
out that restore used that to read old dump tapes, so we broke old dump
So you can't use FreeBSD's unmodified.

So 60011 is OFS_MAGIC and 60012 is NFS_MAGIC. Both of these are variants
on UFS, but really old. And given they are at different offsets, you'll
likely need
to reverse engineer the offsets used for the platform's dinode.

dump from 4.4BSD had 'natural' types (so long was used which would affect
offsets). It seems to be able to read both NFS_MAGIC and OFS_MAGIC tapes,
but you'll likely have to hack together u_spcl that's specific to the
platform which
may take a little trial and error if you don't know what the typedefs for
etc are. There's also a 4.1 dump/restore you might need (available in the
Alpha archive and likely all earlier versions in TUHS).

Without more specific data it's hard to know if there's an extant binary
can be run in emulation to read these tapes.


On Mon, Aug 22, 2022 at 9:35 AM Lars Brinkhoff <> wrote:

> Hello,
> I have on my hands many images of tapes that seems to have been written
> by various implementaions of dump.  I see the magic numbers 60011 and
> 60012 in little and big endian at offsets 18 (16-bit version?) and 24
> (32-bit version?).  I don't know the dating of the tapes, but around
> 1980 would be a reasonable guess.
> Are there some easy to use (ready to run on a modern Unix) tools to
> extract files from such tape files?
> I'm not looking to restore a file system on disk, just extract the
> files.

[-- Attachment #2: Type: text/html, Size: 2175 bytes --]

  reply	other threads:[~2022-08-22 16:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 15:35 [TUHS] " Lars Brinkhoff
2022-08-22 16:27 ` Warner Losh [this message]
2022-08-22 16:53   ` [TUHS] " Bakul Shah
2022-08-22 16:56     ` Warner Losh
2022-08-23  5:55   ` Lars Brinkhoff
2022-08-23 13:02     ` Warner Losh
2022-09-09  5:51   ` Lars Brinkhoff
2022-09-14 17:48     ` Lars Brinkhoff
2022-09-14 21:33       ` Jan-Benedict Glaw
2022-09-15  5:45         ` Lars Brinkhoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).