copy full system from old disk to a new one

Reindl Harald h.reindl at thelounge.net
Tue Feb 19 19:42:59 UTC 2013



Am 19.02.2013 20:24, schrieb Gordan Bobic:
> On 19/02/2013 19:05, Reindl Harald wrote:
>>
>>
>> Am 19.02.2013 20:02, schrieb Gordan Bobic:
>>>> what exactly do you need to align on the partitions?
>>>
>>> For a start, making sure your RAID implementation puts the metadata
>>> at the end of the disk, rather than the beginning.
>>
>> "my RAID implementation"?
>> LINUX SOFTWARE RAID
>>
>> and this is how the raid-partitions are looking
>> no problem since years
>>
>> Disk /dev/sda: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
>> Units = sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x0000ae2c
>>     Device Boot      Start         End      Blocks   Id  System
>> /dev/sda1   *        2048     1026047      512000   fd  Linux raid autodetect
>> /dev/sda2         1026048    31746047    15360000   fd  Linux raid autodetect
>> /dev/sda3        31746048  3906971647  1937612800   fd  Linux raid autodetect
>>
>> [root at srv-rhsoft:/downloads]$ sfdisk -d /dev/sda
>> # partition table of /dev/sda
>> unit: sectors
>> /dev/sda1 : start=     2048, size=  1024000, Id=fd, bootable
>> /dev/sda2 : start=  1026048, size= 30720000, Id=fd
>> /dev/sda3 : start= 31746048, size=3875225600, Id=fd
>> /dev/sda4 : start=        0, size=        0, Id= 0
> 
> That's the MD partition alignment, not the alignment of the FS space within the MD device. The two are not the same.

maybe you should read older posts in the thread

[root at srv-rhsoft:/downloads]$ tune2fs -l /dev/md1
tune2fs 1.42.5 (29-Jul-2012)
Filesystem volume name:   system
Last mounted on:          /
Filesystem UUID:          b935b5db-0051-4f7f-83ac-6a6651fe0988
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg
sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    journal_data_writeback user_xattr acl nobarrier
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1921360
Block count:              7679232
Reserved block count:     0
Free blocks:              5785905
Free inodes:              1728014
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1022
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8176
Inode blocks per group:   511
RAID stride:              128
RAID stripe width:        256
Flex block group size:    16
Filesystem created:       Wed Jun  8 13:10:52 2011
Last mount time:          Fri Feb 15 20:27:01 2013
Last write time:          Fri Feb 15 20:26:59 2013
Mount count:              7
Maximum mount count:      -1
Last checked:             Tue Feb  5 10:23:45 2013
Check interval:           31104000 (12 months)
Next check after:         Fri Jan 31 10:23:45 2014
Lifetime writes:          1279 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
First orphan inode:       1308180
Default directory hash:   half_md4
Directory Hash Seed:      d48fdbd1-5e0c-4dc8-8d0b-7e3c0d6c1e18
Journal backup:           inode blocks

[root at srv-rhsoft:/downloads]$ tune2fs -l /dev/md2
tune2fs 1.42.5 (29-Jul-2012)
Filesystem volume name:   data
Last mounted on:          /tmp
Filesystem UUID:          1abf071b-0c78-4b82-bb21-b3dfb269afa8
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg
sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    journal_data_writeback user_xattr acl nobarrier
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              242204672
Block count:              968805632
Reserved block count:     0
Free blocks:              524215841
Free inodes:              241237943
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      793
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
RAID stride:              128
RAID stripe width:        256
Flex block group size:    16
Filesystem created:       Wed Jun  8 13:10:56 2011
Last mount time:          Fri Feb 15 20:27:03 2013
Last write time:          Fri Feb 15 20:27:03 2013
Mount count:              7
Maximum mount count:      -1
Last checked:             Tue Feb  5 10:23:53 2013
Check interval:           31104000 (12 months)
Next check after:         Fri Jan 31 10:23:53 2014
Lifetime writes:          44 TB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
First orphan inode:       52691565
Default directory hash:   half_md4
Directory Hash Seed:      656f345f-ec1f-4281-82fb-58809a18dad2
Journal backup:           inode blocks


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20130219/33fb8b48/attachment.sig>


More information about the users mailing list