The answer is:
Solaris 2.5 limits filesize to 2GB; ie, home0.dump ran into the
filesize limit. I confused the filesystem limit with the filesize
limit. Solaris 2.6 raises the filesize limit.
Thanks to:
gibian@stars1.hanscom.af.mil (Marc S. Gibian)
cgates@fnoc.navy.mil (Craig Gates)
"Bruce Rossiter" <AROSSITE@us.oracle.com>
darryl@tor.digidyne.ca (Darryl Levesque)
alfred@sequana.com (Alfred Moscola)
Sean Ward <wards@snk077.ast.lmco.com>
leach@OCE.ORST.EDU (Tom Leach)
seeger@cise.ufl.edu (Charles Seeger)
Eugene Kramer <eugene@uniteq.com>
seeger@cise.ufl.edu (Charles Seeger)
Mike Blandford <mikey@nmsu.edu>
Jim Harmon <jharmon@telecnnct.com>
Thanks also for some suggestions to work around the limit:
From: leach@OCE.ORST.EDU (Tom Leach)
Subject: Re: ufsdump to file, 2Gb limit?
Ron, until Solaris 2.6, there is a max file size (not filesystem size) of
2GB. One work around would be to didle the length and density settings to
be just under 2 GB, then when the backup asks for the second (and third)
tapes, you just moved home0.dump to home0.1.dump, (followed by
home0.2.dump and home0.3.dump). Bit of a pain, but at least it's doable.
Tom Leach
leach@oce.orst.edu
From: seeger@cise.ufl.edu (Charles Seeger)
Subject: Re: ufsdump to file, 2Gb limit?
| Does ufsdump have a 2GB limit when dumping to a file? Anyway around it?
Ah, forgot to answer this part. Assuming that you are not massively
exceeding 2GB, you could pipe the dump output through crompress or
gzip. As long as the total compressed size was under 2GB you should
be OK. I'm not sure about restore though. If you are extracting the
entire tape you should be able to zcat into restore. Alternatively,
you could zcat into dd and send it to a device that supports larger
files (e.g. a tape drive) and restore normally. I would be interested
to hear if "zcat <dumpfile> | restore if -" works.
Best,
Chuck
--
Charles Seeger <seeger@cise.ufl.edu>