idc wrote:It may take me a day or two to get to this now as I've exceeded my allotted fiddling with computers time.
idc wrote:Who am I kidding? I've spent the morning copying things across.
Copying root to the ssd went fine. However I am concerned at the number of errors rsync threw up during parts of copying across to the /usr sdhc card. Some folders copied across fine. Others threw up errors like:
'rsync: recv_generator: mkdir "/tmp/car-usr/src/ndiswrapper-1.57" failed: Invalid argument (22)
*** Skipping any contents from this failed directory ***'
or (and I didn't manage to copy all this down before it scrolled off the scree):
'rsync: symlink ... failed: Invalid Argument (22)'
Am I right to be concerned about these? I am a little suspicious of the sdhc card I've used here. (I was having problems with a superblock until I reformatted it; I've bitten the bullet and ordered a new higher capacity sdhc card, which should get here eventually.)
Out of interest would this method of copying the /usr folder across offer any advantage over rsync? Or does rsync use the same underlying method ($find . -depth -print0 | cpio --null --sparse -pvd)?
$ sudo blkid
/dev/sda1: LABEL="ssd" UUID="d9553522-f213-475b-9bc5-5ce8acee5cc1" TYPE="ext4"
/dev/sdb1: LABEL="card usr" UUID="4b54775c-c268-481e-933e-a95f03da2478" TYPE="ext4"
/dev/sdb2: LABEL="card home" UUID="46255024-1bd9-4d9a-8ba7-7d813868a084" TYPE="ext4"
/dev/sdc1: UUID="1de23b16-2066-42cd-9bb9-f49559483aef" TYPE="ext4"
/dev/sdc5: UUID="8905bdc2-9b38-456b-a57b-6696c8a2af0f" TYPE="swap"
$ cat /etc/fstab
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
UUID=d9553522-f213-475b-9bc5-5ce8acee5cc1 / ext4 errors=remount-ro 0 1
UUID=4b54775c-c268-481e-933e-a95f03da2478 /usr ext4 defaults 0 1
UUID=46255024-1bd9-4d9a-8ba7-7d813868a084 /home ext4 defaults 0 1
UUID=8905bdc2-9b38-456b-a57b-6696c8a2af0f none swap sw 0 0
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 3.7G 761M 2.8G 22% /
udev 1001M 8.0K 1001M 1% /dev
tmpfs 403M 992K 402M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1007M 128K 1007M 1% /run/shm
/dev/sdb1 3.7G 3.0G 570M 85% /usr
/dev/sdb2 3.7G 323M 3.2G 10% /home
/dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/sdb1 on /usr type ext4 (rw,commit=0)
/dev/sdb2 on /home type ext4 (rw,commit=0)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/bam/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=bam)
I just replicated what you are doing using a mint Mint 12 installation. Worked fine. rsync had no problems at all. So I suspect it is your card.
Users browsing this forum: taikara and 2 guests