partitions disappear on running act_prep script
Opened this issue · 3 comments
Followed the instructions and created partitions on my nvme drives. as per this link https://github.com/aerospike/act
As soon as I run act_prep script, all the partitions disappear.
`[root@PCI27 ~]# ls -1 /dev/nvme*
/dev/nvme0
/dev/nvme0n1
/dev/nvme0n1p1
/dev/nvme0n1p10
/dev/nvme0n1p11
/dev/nvme0n1p12
/dev/nvme0n1p13
/dev/nvme0n1p14
/dev/nvme0n1p15
/dev/nvme0n1p16
/dev/nvme0n1p17
/dev/nvme0n1p18
/dev/nvme0n1p19
/dev/nvme0n1p2
/dev/nvme0n1p20
/dev/nvme0n1p21
/dev/nvme0n1p22
/dev/nvme0n1p23
/dev/nvme0n1p24
/dev/nvme0n1p25
/dev/nvme0n1p26
/dev/nvme0n1p27
/dev/nvme0n1p28
/dev/nvme0n1p29
/dev/nvme0n1p3
/dev/nvme0n1p30
/dev/nvme0n1p31
/dev/nvme0n1p32
/dev/nvme0n1p4
/dev/nvme0n1p5
/dev/nvme0n1p6
/dev/nvme0n1p7
/dev/nvme0n1p8
/dev/nvme0n1p9
/dev/nvme1
/dev/nvme1n1
/dev/nvme1n1p1
/dev/nvme1n1p10
/dev/nvme1n1p11
/dev/nvme1n1p12
/dev/nvme1n1p13
/dev/nvme1n1p14
/dev/nvme1n1p15
/dev/nvme1n1p16
/dev/nvme1n1p17
/dev/nvme1n1p18
/dev/nvme1n1p19
/dev/nvme1n1p2
/dev/nvme1n1p20
/dev/nvme1n1p21
/dev/nvme1n1p22
/dev/nvme1n1p23
/dev/nvme1n1p24
/dev/nvme1n1p25
/dev/nvme1n1p26
/dev/nvme1n1p27
/dev/nvme1n1p28
/dev/nvme1n1p29
/dev/nvme1n1p3
/dev/nvme1n1p30
/dev/nvme1n1p31
/dev/nvme1n1p32
/dev/nvme1n1p4
/dev/nvme1n1p5
/dev/nvme1n1p6
/dev/nvme1n1p7
/dev/nvme1n1p8
/dev/nvme1n1p9
/dev/nvme2
/dev/nvme2n1
/dev/nvme2n1p1
/dev/nvme2n1p10
/dev/nvme2n1p11
/dev/nvme2n1p12
/dev/nvme2n1p13
/dev/nvme2n1p14
/dev/nvme2n1p15
/dev/nvme2n1p16
/dev/nvme2n1p17
/dev/nvme2n1p18
/dev/nvme2n1p19
/dev/nvme2n1p2
/dev/nvme2n1p20
/dev/nvme2n1p21
/dev/nvme2n1p22
/dev/nvme2n1p23
/dev/nvme2n1p24
/dev/nvme2n1p25
/dev/nvme2n1p26
/dev/nvme2n1p27
/dev/nvme2n1p28
/dev/nvme2n1p29
/dev/nvme2n1p3
/dev/nvme2n1p30
/dev/nvme2n1p31
/dev/nvme2n1p32
/dev/nvme2n1p4
/dev/nvme2n1p5
/dev/nvme2n1p6
/dev/nvme2n1p7
/dev/nvme2n1p8
/dev/nvme2n1p9
/dev/nvme3
/dev/nvme3n1
/dev/nvme3n1p1
/dev/nvme3n1p10
/dev/nvme3n1p11
/dev/nvme3n1p12
/dev/nvme3n1p13
/dev/nvme3n1p14
/dev/nvme3n1p15
/dev/nvme3n1p16
/dev/nvme3n1p17
/dev/nvme3n1p18
/dev/nvme3n1p19
/dev/nvme3n1p2
/dev/nvme3n1p20
/dev/nvme3n1p21
/dev/nvme3n1p22
/dev/nvme3n1p23
/dev/nvme3n1p24
/dev/nvme3n1p25
/dev/nvme3n1p26
/dev/nvme3n1p27
/dev/nvme3n1p28
/dev/nvme3n1p29
/dev/nvme3n1p3
/dev/nvme3n1p30
/dev/nvme3n1p31
/dev/nvme3n1p32
/dev/nvme3n1p4
/dev/nvme3n1p5
/dev/nvme3n1p6
/dev/nvme3n1p7
/dev/nvme3n1p8
/dev/nvme3n1p9
[root@FM21V213-PCI27 ~]# cd act/target/bin/
[root@FM21V213-PCI27 bin]# sudo ./act_prep /dev/nvme0
nvme0 nvme0n1p13 nvme0n1p19 nvme0n1p24 nvme0n1p3 nvme0n1p6
nvme0n1 nvme0n1p14 nvme0n1p2 nvme0n1p25 nvme0n1p30 nvme0n1p7
nvme0n1p1 nvme0n1p15 nvme0n1p20 nvme0n1p26 nvme0n1p31 nvme0n1p8
nvme0n1p10 nvme0n1p16 nvme0n1p21 nvme0n1p27 nvme0n1p32 nvme0n1p9
nvme0n1p11 nvme0n1p17 nvme0n1p22 nvme0n1p28 nvme0n1p4
nvme0n1p12 nvme0n1p18 nvme0n1p23 nvme0n1p29 nvme0n1p5
[root@FM21V213-PCI27 bin]# sudo ./act_prep /dev/nvme0n1 &
[1] 8590
[root@PCI27 bin]# /dev/nvme0n1 size = 7681501126656 bytes, 58605202 large blocks
cleaning device /dev/nvme0n1
................
##Ran the below steps on all my 4 drives
sudo ./act_prep /dev/nvme0n1 &
sudo ./act_prep /dev/nvme1n1 &
sudo ./act_prep /dev/nvme2n1 &
sudo ./act_prep /dev/nvme3n1 &
Then I check for partitions again and this is what I see
[root@PCI27 bin]# ls -1 /dev/nvme*
/dev/nvme0
/dev/nvme0n1
/dev/nvme1
/dev/nvme1n1
/dev/nvme2
/dev/nvme2n1
/dev/nvme3
/dev/nvme3n1
[root@PCI27 bin]#`
The partition table lives on the disk.
If you intend to use partitions, you should act_prep before making partitions or only target the partitions for act_prep.
If you partition before running act_prep, running act_prep against the base device deletes all those partitions - in this case you partition nvme0n1 into nvme0n1p1...etc, you would only act_prep nvme0n1p1..etc NOT nvme0n1.
I recently submitted an MR that talks a little about partitions if you want to reference that. https://github.com/aerospike/act/pull/54/files as I think you may have too many