| 1 |
> Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes |
| 2 |
> 255 heads, 63 sectors/track, 243201 cylinders |
| 3 |
> Units = cylinders of 16065 * 512 = 8225280 bytes |
| 4 |
> Sector size (logical/physical): 512 bytes / 512 bytes |
| 5 |
|
| 6 |
A small caveat -- if this is an "advanced format" drive be sure to use |
| 7 |
fdisk in sector mode (fdisk -uc) and start the first partition on a |
| 8 |
sector number which is a multiple of 8. |
| 9 |
|
| 10 |
(Yes, I know it says "512 bytes physical sector size" above, but all |
| 11 |
five of my 1TB AF WD greens happily advertise a 512 byte physical sector |
| 12 |
size) |
| 13 |
|
| 14 |
>> Ok now I was going to use same reiserfs < no big deal> |
| 15 |
>> unless I can use reiser4? good idea? <discuss-caveats> |
| 16 |
|
| 17 |
Assuming you care about your data, my advice is to drop reiserfs for |
| 18 |
everything but unimportant, easily replaceable stuff (like |
| 19 |
/usr/portage). Reiserfs undoubtedly has performance advantages in some |
| 20 |
areas, but its structure is more prone to damage and it has lousy fs |
| 21 |
utils. Ext4 might be slower at times but it is backed by a very well |
| 22 |
tested and maintained fsck. |
| 23 |
Reiser4? Not a chance in hell. |
| 24 |
|
| 25 |
> Just replace "/dev/sdb1" with "LABEL=boot" |
| 26 |
|
| 27 |
Small caveat: labels in /etc/fstab are ok (even for swap partitions, |
| 28 |
just create them with mkswap -L), but you must still use a device name |
| 29 |
in the "root" parameter on the kernel command line. Labels/UUIDs are not |
| 30 |
supported there. |
| 31 |
|
| 32 |
> Another approach (less readable but arguably less easy to break) is |
| 33 |
> using "UUID=...". You can find these out with dumpe2fs. I guess |
| 34 |
> something similar exists for reiserfs, as well. |
| 35 |
|
| 36 |
or just ls -al /dev/disk/by-uuid |
| 37 |
|
| 38 |
>> dd if=/dev/sda of=/dev/sdb bs=32768 |
| 39 |
|
| 40 |
Definitely not. Sure, you can grow the fs to fill the partition |
| 41 |
aftwerwards (resize2fs or its reiser equivalent), but you will be |
| 42 |
wasting time and taking unnecessary risks. |
| 43 |
Boot from a livecd, create a new filesystem on the target, mount both |
| 44 |
filesystems and use |
| 45 |
|
| 46 |
rsync -aHPv /path/to/old/mountpoint/ /path/to/new/mountpoint/ |
| 47 |
or simply |
| 48 |
tar c /path/to/old/ | tar xvp /path/to/new |
| 49 |
|
| 50 |
rsync can show you the progress of the operation, which is nice, but it |
| 51 |
is not available on all live cds (for example, gentoo-minimal did not |
| 52 |
ship with it last time I checked). If you use rsync, pay special |
| 53 |
attention to the -H option as -a (archive mode) does not preserve hard |
| 54 |
links by default. |
| 55 |
|
| 56 |
HTH, |
| 57 |
andrea |
Archives