xfs
[Top] [All Lists]

Re: Strange system behaviour when copying disks

To: Steve Lord <lord@xxxxxxx>
Subject: Re: Strange system behaviour when copying disks
From: Rusell Cattelan <cattelan@xxxxxxx>
Date: 14 May 2003 15:01:40 -0500
Cc: Olaf Frączyk <olaf@xxxxxxxxxxxxx>, Seth Mos <knuffie@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <1052928863.3525.189.camel@xxxxxxxxxxxxxxxxxxxx>
Organization:
References: <4.3.2.7.2.20030514170300.037b8840@xxxxxxxxxxxxx> <1052928610.896.9.camel@venus> <1052928863.3525.189.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Wed, 2003-05-14 at 11:14, Steve Lord wrote:
> On Wed, 2003-05-14 at 11:10, Olaf FrDczyk wrote:
> > On Wed, 2003-05-14 at 17:54, Seth Mos wrote:
> > > May I suggest the following procedure for copying disks and information...
> > Why it should be better?
> > Doing 'cat' I have perfect copy of disk.
> > You think that I will get lower latency with your scenario?
> > > partition the second disk similar to your first.
> > > Mount these partition under something like /mnt/new
> > > And the other partitions underneath that... eg.
> > > mount /dev/hdc1 /mnt/new
> > > mount /dev/hdc5 /mnt/new/usr
> > > 
> > > After completing this procedure you can transfer the data.
> > > 
> > > (cd /;tar -cf - .)|(cd /mnt/new;tar -xf -)
> > 
> > And all my ACLs go to hell :)
> > BTW try to do it with NTFS partition :(
> > 
> > > This will give you all files on the second disk. However you must 
> > > reinstall 
> > > lilo on this disk since it will not be in the same place anymore.
> > These disks are not used for booting, OS etc.
> > 
> > > Not it should not be enough to make it that severe. I suspect the dma 
> > > issue.
> > As I said earlier, they have DMA enabled.
> > 
> > Regards,
> > 
> > Olaf
> > 
> > 
> 
> 
> Seth is suggesting copying the contents of the filesystem, not the
> complete device. What you really need is xfs_copy implemented on
> linux I think, failing that xfs_dump piped into xfs_restore which
> will keep acls.
xfs_copy might be working... give it a try.

> 
> Steve
> 


<Prev in Thread] Current Thread [Next in Thread>