home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.admin
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!eng.ufl.edu!news
- From: ruck@zeta.ee.ufl.edu (John R Ruckstuhl Jr)
- Subject: Re: Fastest way to transfer whole filesystems?
- Message-ID: <1992Nov21.102026.8285@eng.ufl.edu>
- Sender: news@eng.ufl.edu (Usenet Diskhog System)
- Organization: EE Dept at UF
- References: <40335@unix.SRI.COM> <1992Nov16.064402.9186@cssc-syd.tansu.com.au> <panissec.722053148@bag_end>
- Date: Sat, 21 Nov 92 10:20:26 GMT
- Lines: 35
-
- In article <panissec.722053148@bag_end> panissec@nms.otca.oz.au (Colin Panisset) writes:
- > rodney@cssc-syd.tansu.com.au (Rodney Campbell) writes:
- > }cole@unix.SRI.COM (Susan Cole) writes:
- > }>What's the fastest way to transfer an entire filesystem from one
- > }>disk partition to another (different type disk, larger partition)?
-
- > You will find, however, that this creates a duplicate filesystem that actually
- > uses more space than did the original. This is due to the block allocation
- > methods used when tar and cpio both do their restore.
-
- > Instead, use dump & restore - you'll get an exact duplicate of the original,
- > inode for inode - and with the same degree of fragmentation as the original.
-
-
- NOT NECESSARILY ?
-
- I noticed when that when I duplicated filesystems with dump & restore,
- the duplicate was NOT exactly as the original --
-
- I don't know the correct terminology to describe this, but, you know how
- you make extra space in the lost+found directory structure for a
- filesystem, so that fsck will have plenty of slots to put junk,
-
- well the dump & restore didn't preserve that bloated lost+found.
-
- So, you may want to go back and re-bloat. :)
-
- I'm using SunOS 4.1.1
-
- Regards,
- ruck
- --
- John R. Ruckstuhl, Jr. ruck@alpha.ee.ufl.edu
- Dept of Electrical Engineering ruck@cis.ufl.edu, uflorida!ruck
- University of Florida ruck%sphere@cis.ufl.edu, sphere!ruck
-