[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Squeeze installation fdisk bug



On Tue, Feb 1, 2011 at 9:31 PM, tv.debian@googlemail.com
<tv.debian@googlemail.com> wrote:
>
> Regarding "sfdisk -d", if you ran this command with a filesystem already
> on the source drive you'll run into problems due to the filesystem
> boundaries being misplaced.
>

Thanks for the reply but I did not get it full :-(

The source drive was /dev/sda It is a running RAID1 partition.
I connected sdb and did

#sfdisk -d /dev/sda | sfdisk -f /dev/sdb

to create identical partitions on sdb and then added it to the RAID device by

#mdadm -a /dev/md0 /dev/sdb1
#mdadm -a /dev/md1 /dev/sdb2
#mdadm -a /dev/md2 /dev/sdb3
#mdadm -a /dev/md3 /dev/sdb4

and the RAID devices now look like


 root@vmsrv:~# cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sdb4[2] sda4[0]
      470514552 blocks super 1.2 [2/2] [UU]

md2 : active raid1 sdb3[2] sda3[0]
      16599992 blocks super 1.2 [2/2] [UU]

md1 : active raid1 sdb2[2] sda2[0]
      976884 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sdb1[2] sda1[0]
      291828 blocks super 1.2 [2/2] [UU]

unused devices: <none>
root@vmsrv:~#

'parted -l'  looks like

=========
Model: ATA ST3500418AS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  300MB   299MB   primary               raid
 2      300MB   1300MB  1000MB  primary               raid
 3      1300MB  18.3GB  17.0GB  primary               raid
 4      18.3GB  500GB   482GB   primary               raid


Model: ATA ST3500418AS (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  300MB   299MB   primary               raid
 2      300MB   1300MB  1000MB  primary               raid
 3      1300MB  18.3GB  17.0GB  primary               raid
 4      18.3GB  500GB   482GB   primary               raid


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-backup: 53.7GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  53.7GB  53.7GB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-lxc: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  107GB  107GB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-vms: 116GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  116GB  116GB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-var: 5000MB
Sector size (logical/physical): 512B/512B


>Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  5000MB  5000MB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-usr: 1996MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  1996MB  1996MB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-tmp: 96.5MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  96.5MB  96.5MB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-home: 96.5MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  96.5MB  96.5MB  jfs


Model: Linux Software RAID Array (md)
Disk /dev/md0: 299MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  299MB  299MB  ext3


Model: Linux Software RAID Array (md)
Disk /dev/md1: 1000MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  1000MB  1000MB  ext3


Model: Linux Software RAID Array (md)
Disk /dev/md2: 17.0GB
Sector size (logical/physical): 512B/512B

Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  1996MB  1996MB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-tmp: 96.5MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  96.5MB  96.5MB  jfs


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vg0-home: 96.5MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  96.5MB  96.5MB  jfs


Model: Linux Software RAID Array (md)
Disk /dev/md0: 299MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  299MB  299MB  ext3


Model: Linux Software RAID Array (md)
Disk /dev/md1: 1000MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  1000MB  1000MB  ext3


Model: Linux Software RAID Array (md)
Disk /dev/md2: 17.0GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system     Flags
 1      0.00B  17.0GB  17.0GB  linux-swap(v1)


Error: /dev/md3: unrecognised disk label

root@vmsrv:~#

Is this dangerous?

Thanks

--Siju


Reply to: