From: sms@2BSD.COM (Steven M. Schultz)
Subject: [pups] missing space in 2.11_rp_unknown
Date: Tue, 26 Feb 2002 15:29:07 -0800 (PST) [thread overview]
Message-ID: <200202262329.g1QNT7T07646@moe.2bsd.com> (raw)
Hi!
> From: Christian Groessler <cpg at aladdin.de>
> > Did you use dump+restor?
>
> No, tar. I tried again with dump and restor and now it works! Thanks
> for the hint! I seldomly use dump/restore.
Ah ha! For moving filesystems dump+restor or 'afio' need to be
used. Dump+restor also have the advantage of preserving the
file flags (see chflags(2) and chflags(1)) - other utilities do
not preserve that metadata.
The other thing that dump+restor (or afio) handle correctly is
the special files in /dev. 'tar' does not know how to archive
files such as "/dev/rp0a".
Mmmm, I wonder if the problems you were having were caused by
/dev not being correctly populated.
> Now there's enough space in /:
>
> $ df
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/xp0a 7816 2658 5158 04% /
> /dev/xp0g 151625 117599 34026 08% /usr
> $
>
> Btw, the capacity values look a bit strange?
Yes, they do look (more than a little bit) strange.
On my system here (a P11 based emulated PDP-11 - I have a real 11/73
but it is only powered up when I'm actively testing):
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/xp0a 8228 3163 5065 38% /
/dev/xp0h 155328 84188 71140 54% /usr
What patchlevel did you mention the system was at? There were a lot
of patches issued after the ' 2.11_rp_unknown' image was created.
One thing, which probably will not make any difference, to try would
be to recompile 'df' (and possibly 'libc') and see if the problem
changes. Looks like it's a math error of some kind so either
the compiler/libraries are broken or P11's having a problem doing
arithmetic.
Cheers,
Steven Schultz
sms at 2bsd.com
next reply other threads:[~2002-02-26 23:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 23:29 Steven M. Schultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 16:38 Christian Groessler
2002-03-03 9:47 Steven M. Schultz
2002-03-01 22:28 Christian Groessler
2002-02-28 16:53 Steven M. Schultz
2002-02-28 16:32 Christian Groessler
2002-02-27 23:25 Steven M. Schultz
2002-02-28 2:24 ` Frank Wortner
2002-02-27 21:35 Christian Groessler
2002-02-26 11:56 Christian Groessler
2002-02-25 17:16 Steven M. Schultz
2002-02-25 11:57 Christian Groessler
2002-02-23 3:31 Steven M. Schultz
2002-02-22 14:52 Christian Groessler
2002-02-23 1:29 ` Greg Lehey
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202262329.g1QNT7T07646@moe.2bsd.com \
--to=sms@2bsd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).