home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!ames!data.nas.nasa.gov!taligent!apple!mumbo.apple.com!gallant.apple.com!chuq
- From: chuq@gallant.apple.com (Chuq Von Rospach)
- Newsgroups: comp.unix.aux
- Subject: Re: rdump/dump.bsd --> bad sblock magic number
- Message-ID: <1992Aug27.220048.21817@gallant.apple.com>
- Date: 27 Aug 92 22:00:48 GMT
- References: <khj.714865647@beagle>
- Organization: I is a writur
- Lines: 37
-
- khj@cs.appstate.edu (Kenneth H. Jacker) writes:
-
- > # rdump 0uf sc:/dev/rmt0h /
- > DUMP: Date of this level 0 dump: Wed Aug 26 16:25:02 1992
- > DUMP: Date of last level 0 dump: the epoch
- > DUMP: Dumping / to /dev/rmt0h on host sc
- > ==> DUMP: bad sblock magic number
- > DUMP: The ENTIRE dump is aborted.
-
- bad sblock messages usually mean that whatever you're trying to dump doesn't
- have a superblock. Every time I've seen it it's because of a problem in the
- parameter list (i.e. a typo).
-
- In this case, it's because the file specification is wrong. A/UX's dump.bsd
- doesn't understand '/' as a filesystem, opens up '/' as a special device and
- tries to read the superblock out of it, which doesn't work.
-
- instead of
-
- # dump.bsd 0uf /dev/null /
-
- you should use
-
- # dump.bsd 0uf /dev/null /dev/dsk/c0d0s0
-
- and it'll work (at least, on my box).
-
- Note: some versions of dump do accept '/', others don't. This one doesn't.
- Confusing as hell until you figure it out, but invariably the sblock
- message is because whatever filespec it's given to back up isn't a special
- device.
-
- --
- Chuq "IMHO" Von Rospach, ESD Support & Training (DAL/AUX) =+= Member, SFWA
- chuq@apple.com | GEnie: MAC.BIGOT | ALink:CHUQ =+= Editor, OtherRealms
- A real SF writur with stories in ALTERNATE KENNEDYS and THE
- FURTHER ADVENTURES OF BATMAN, in better bookstores now!
-