zGreenfelder wrote:
/dev/mapper/nvidia_baaccajap7 37G 29G 6.2G 83% /home
/dev/mapper/nvidia_baaccajap12 581G 56G 496G 11% /data /dev/mapper/nvidia_baaccajap11 7.1G 145M 6.6G 3% /home/david/pvt
Plan:
cp -a /home /data
I think I'd change to -Rp or use a dual tar method...
Err, have you read the man page that explains what -a means?
Why do people not trust cp? It's a fine program that does what it says on the tin. There's a lot more to go wrong using tar.
Lew Wolfgang wrote:
Using cp for moving partitions makes me nervous, especially if there are symbolic links in the source side (by default, cp copies the contents of symlinks, rather than the symlink itself. This can lead to recursion that fills up a disk). Also, I'd want to unmount /home, then remount on /mnt, just to make sure it's quiescent. I'm rather fond of a tar pipeline for this kind of thing,
Err, have you read the man page that explains what -a means?
Why do people not trust cp? It's a fine program that does what it says on the tin. There's a lot more to go wrong using tar.
Also, rsync is a more modern way of safely doing the deed:
rsync is also a fine program. But for local file copying, cp is the tool designed for the job.
Cheers, Dave
fwiw re using cp, from an old SuSE article on moving a directory to a larger partition, using /home as an example, as root. (I couldn't find the url, 1. Make and format partition 2. cd /home 3. mkdir /newhome 4. mount <new partition> /newhome 5. cp -axv . /newhome 6. verify copy 7. mv /home /home.old 8. mkdir /home 9. edit fstab to show new partition mounted at /home 10. reboot 11. check new partition has mounted 12. cd / 13. rm -fr home.old The cp options insure the copy is recursive, keeps properties, includes symlinks, write to stdout all filenames (so could be redirected to a file for reference). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org