From: vr on 10 Apr 2010 17:20 What's the best mechanism to migrate a working bootable system from one drive to a smaller capacity drive? e.g. take this 226G filesystem df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb1 226G 4.1G 210G 2% / tmpfs 3.0G 0 3.0G 0% /lib/init/rw udev 3.0G 244K 3.0G 1% /dev tmpfs 3.0G 0 3.0G 0% /dev/shm and transfer it onto say a 32G drive? -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/3cc33b52b344d44be33167a82fe301fe(a)192.168.0.66
From: Sjoerd Hardeman on 10 Apr 2010 17:30 vr schreef: > What's the best mechanism to migrate a working bootable system from one > drive to a smaller capacity drive? > > e.g. take this 226G filesystem > > df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sdb1 226G 4.1G 210G 2% / > tmpfs 3.0G 0 3.0G 0% /lib/init/rw > udev 3.0G 244K 3.0G 1% /dev > tmpfs 3.0G 0 3.0G 0% /dev/shm > > and transfer it onto say a 32G drive? mount the new device (mount -odev /dev/newdevice), and do a rsync -ax / /media/newdevice. Then do a chroot /media/newdevice, grub-install /dev/newdevice Sjoerd
From: Clive McBarton on 11 Apr 2010 09:10 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sjoerd Hardeman wrote: > mount the new device (mount -odev /dev/newdevice), and do a > rsync -ax / /media/newdevice. What exactly is the advantage of this approach over "cp -a" or "mv"? I would have suggested mv. It has the useful property that you can easily spot aborted transfers by the fact that the original device is not empty afterwards. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvBymgACgkQ+VSRxYk440+GBQCgq0EvrFUI7Hm4A8Q73ncz7KTF 51UAn0weYuo1nka6TqTxggBp4Y/tzA8O =QZnM -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BC1CA69.4080601(a)web.de
From: Eduardo M KALINOWSKI on 11 Apr 2010 09:20 On 04/11/2010 10:11 AM, Clive McBarton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sjoerd Hardeman wrote: > >> mount the new device (mount -odev /dev/newdevice), and do a >> rsync -ax / /media/newdevice. >> > What exactly is the advantage of this approach over "cp -a" or "mv"? > Over mv? That you keep the original files. Over cp? That you can resume from where you left off in case the transfer is stopped for any reason. -- Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec Eduardo M KALINOWSKI eduardo(a)kalinowski.com.br -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BC1CA98.4070100(a)kalinowski.com.br
From: Clive McBarton on 11 Apr 2010 09:30
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eduardo M KALINOWSKI wrote: >>> mount the new device (mount -odev /dev/newdevice), and do a >>> rsync -ax / /media/newdevice. >>> >> What exactly is the advantage of this approach over "cp -a" or "mv"? >> > > Over mv? That you keep the original files. Of course. But in this case the OP said "migrate". > Over cp? That you can resume from where you left off in case the > transfer is stopped for any reason. Useful point. With cp you'd have to start over. What are the disadvantages of rsync? E.g., doesn't it compress and decompress everything, hence hogging the CPU and possibly slowing transfers? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvBzscACgkQ+VSRxYk4409N6QCg2H+F4XhpS/eRmSUaxiFAZG5v nNUAoL1+BijzOvhecWOzULmWvIBJ2Nyb =FU3d -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BC1CEC7.7030909(a)web.de |