> create /home on /hda3
Not quite. /dev/hda3 should contain user1/ user2/ user3/ which are the directories which are on /dev/hda1 as /home/user1 /home/user2 /home/user3 You then mount /dev/hda3 /home The UUID and volume label can be used as alternative ways to identify /dev/hda3. This is worthwhile doing as the volume name might change depending what kernel you are running (thanks to changes in the ATA disk handling). e2label /dev/hda3 /home mount LABEL=/home /home The distinction between label and UUID only matters in a storage area network. I suggest you do all this in single user mode and use the explicit mount command rather than rebooting until you have verified that everything (especially dot-files, ownerships and permissions) is just right. You can always umount /home, mfks /dev/hda3, mount /dev/hda3 /mnt and try the tar/rsync again. Then edit /etc/fstab to reflect the contents of the mount command. Then reboot with a recovery CD in hand (mis-editing fstab is one way to really break a machine). > Everything was so much easier before UUID. Just think of it as a filesystem label which is generated by the operating system rather than chosen by you. It's not very useful when you actually know the disk's name, as you do here, so just use the disk name whilst doing mounting for the copy. When you add the disk to fstab use whatever UUID mkfs placed on the filesystem. This allows the boot process to deal with disks which have changed name (because their address on the SAN has changed, you've moved ATA cables around, etc). Thoughts vary whether the filesystem label or the UUID is best to use in fstab. In your case there is no possible collision of names and it doesn't matter. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
