home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!sun-barr!news2me.EBay.Sun.COM!exodus.Eng.Sun.COM!sun!amdcad!hobbes!ericw
- From: ericw@hobbes.amd.com (Eric Wedaa)
- Newsgroups: comp.unix.admin
- Subject: Re: Best method for filesystem copy?
- Message-ID: <ericw.724458671@hobbes>
- Date: 15 Dec 92 22:31:11 GMT
- References: <1992Dec8.144945.6339@nsisrv.gsfc.nasa.gov>
- Sender: usenet@amd.com (NetNews)
- Organization: Advanced Micro Devices, Inc.
- Lines: 36
- Nntp-Posting-Host: hobbes
-
- markb@news.gsfc.nasa.gov (Mark R. Baith) writes:
-
-
- >I need to copy a filesystem currently housed on a 1 Gb disk to a 2 Gb
- >disk. dump seemed like a good idea, but the procedure kept asking for
-
- Well, Considering that I do this sort of stuff every week (Or so it
- seems...) here's what I do...
-
- cd from_dir
- tar -cf - |(cd target_dir; tar -xfBp -)
-
- or...
-
- rsh from_machine
- cd from_dir
- tar -cf - |rsh target_machine "(cd target_dir; tar -xfBp -)"
-
- Their are two things to remember though:
- 1) core files grow because of tar (They are "holey" files.)
- 2) device files/pipes do not get copied.
-
- On the other hand, if my users lose a pipe, it's no big deal.
- They don't typically keep core files around.
- They don't have device files in their directories either.
-
- >>>>>>>Ericw
- (BTW: why would I be doing this every week? Because I have an AUSPEX
- and users that love disk space! ;)
-
-
- --
- Eric Wedaa - eric.wedaa@amd.com | Two more kinds of lies...
- {ames apple uunet}!amd!ericw | Release Dates, and Benchmarks
- Advanced Micro Devices, M/S 167 PO Box 3453 Sunnyvale, CA 94088-3453
- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-