setup left in an unrecoverable state

[bpbp-boop]

I was following the Getting Started Guide and adding additional storage for Docker. Running docker-storage-setup results in the same issue. I'm not sure how to recover from this except to start again from scratch.

-bash-4.3# systemctl status docker-storage-setup
● docker-storage-setup.service - Docker Storage Setup
   Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Fri 2016-07-01 06:02:04 UTC; 13min ago
  Process: 1010 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=0/SUCCESS)
 Main PID: 1010 (code=exited, status=0/SUCCESS)

Jul 01 06:02:03 atomic01 systemd[1]: Starting Docker Storage Setup...
Jul 01 06:02:03 atomic01 docker-storage-setup[1010]: INFO: Device /dev/xvdb is already partitioned and is part of
Jul 01 06:02:03 atomic01 docker-storage-setup[1010]: NOCHANGE: partition 2 could only be grown by 4096 [fudge=204
Jul 01 06:02:03 atomic01 docker-storage-setup[1010]:   Physical volume "/dev/xvda2" changed
Jul 01 06:02:03 atomic01 docker-storage-setup[1010]:   1 physical volume(s) resized / 0 physical volume(s) not re
Jul 01 06:02:03 atomic01 docker-storage-setup[1010]: NOCHANGE: partition 1 is size 104855552. it cannot be grown
Jul 01 06:02:04 atomic01 docker-storage-setup[1010]:   Physical volume "/dev/xvdb1" changed
Jul 01 06:02:04 atomic01 docker-storage-setup[1010]:   1 physical volume(s) resized / 0 physical volume(s) not re
Jul 01 06:02:04 atomic01 docker-storage-setup[1010]:   Logical volume "docker-pool" changed.
Jul 01 06:02:04 atomic01 systemd[1]: Started Docker Storage Setup.

-bash-4.3# lsblk
NAME                            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sr0                              11:0    1  366K  0 rom  
xvda                            202:0    0    6G  0 disk 
|-xvda1                         202:1    0  300M  0 part /boot
`-xvda2                         202:2    0  5.7G  0 part 
  |-atomicos-root               253:0    0    3G  0 lvm  /sysroot
  |-atomicos-docker--pool_tmeta 253:1    0    8M  0 lvm  
  | `-atomicos-docker--pool     253:3    0    2G  0 lvm  
  `-atomicos-docker--pool_tdata 253:2    0    2G  0 lvm  
    `-atomicos-docker--pool     253:3    0    2G  0 lvm  
xvdb                            202:16   0   50G  0 disk 
`-xvdb1                         202:17   0   50G  0 part 

-bash-4.3# pvdisplay 
  --- Physical volume ---
  PV Name               /dev/xvda2
  VG Name               atomicos
  PV Size               5.71 GiB / not usable 2.00 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              1460
  Free PE               194
  Allocated PE          1266
  PV UUID               iDbzdH-fk4e-zEUU-MB5A-hYUe-1jsN-LWc9sn

  --- Physical volume ---
  PV Name               /dev/xvdb1
  VG Name               atomicos
  PV Size               50.00 GiB / not usable 2.00 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              12799
  Free PE               12799
  Allocated PE          0
  PV UUID               Qjw5Ae-idYh-OTcE-JQhF-OYXz-iIrM-cttUdw

-bash-4.3# vgdisplay 
  --- Volume group ---
  VG Name               atomicos
  System ID             
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  36
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               1
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               55.70 GiB
  PE Size               4.00 MiB
  Total PE              14259
  Alloc PE / Size       1266 / 4.95 GiB
  Free  PE / Size       12993 / 50.75 GiB
  VG UUID               Y9utfV-znP8-hh17-FCmx-Myfx-3ajH-nV7EUV

-bash-4.3# lvdisplay 
  --- Logical volume ---
  LV Path                /dev/atomicos/root
  LV Name                root
  VG Name                atomicos
  LV UUID                AyU3qA-gzpE-Qf0D-fqDu-Vz65-y5Mi-lS0c1c
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain, 2016-06-07 05:16:37 +0000
  LV Status              available
  # open                 1
  LV Size                2.93 GiB
  Current LE             750
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

  --- Logical volume ---
  LV Name                docker-pool
  VG Name                atomicos
  LV UUID                seCdR8-brGh-Ly4C-hqZb-8cFi-YORJ-zyuF8W
  LV Write Access        read/write
  LV Creation host, time localhost.localdomain.localdomain, 2016-07-01 04:29:26 +0000
  LV Pool metadata       docker-pool_tmeta
  LV Pool data           docker-pool_tdata
  LV Status              available
  # open                 0
  LV Size                2.00 GiB
  Allocated pool data    51.03%
  Allocated metadata     7.47%
  Current LE             512
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

[eburgueno]

@bpbp-boop In this case you can just remove the secondary disk from the atomicos VG: vgreduce atomicos /dev/xvdb1 (you'll need to run docker-storage-setup --reset first to delete the LV).

If what you want is to have a separate volume group altogether for Docker, you need to edit /etc/sysconfig/docker-storage-setup before adding the second disk to the VM, because docker-storage-setup runs at boot.

[rhvgoyal]

@bpbp-boop Messages you have output are truncated. Try using "-l".

So what's the problem you are facing? I did not understand it yet.