volume resize does not works as expected for Vertica
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Critical
|
Sushil Kumar |
Bug Description
while testing volume resize with vertica found that found that because of an incomplete unmount the resize fails
while debugging the situation found that mount-point never got unmount in gues
ubuntu@test-1:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 19G 1.6G 17G 9% /
udev 998M 12K 998M 1% /dev
tmpfs 201M 220K 201M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1002M 0 1002M 0% /run/shm
/dev/vdb 1008M 70M 887M 8% /var/lib/vertica
tried to do that manually and it suggested that device is busy
ubuntu@test-1:~$ sudo umount /dev/vdb
umount: /var/lib/vertica: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
and on tracing the process occupying the disk found that guestagent itself is holding locks over the disk
ubuntu@test-1:~$ fuser -vm /dev/vdb
/dev/vdb: root kernel mount /dev
after i stopped trove-guest service found that now kernel blocks probably because what all happened after incomplete unmount
ubuntu@test-1:~$ fuser -vm /dev/vdb
/dev/vdb: root kernel mount /dev
probably failure was not detected by the pexpect process which originally tried to do it in actual place from volume.py, which is why next scenarios came in existence
Reverified the pexpect way of unmounting, and it does not show any error
>>> import pexpect
>>> cmd = "sudo umount %s" % "/dev/vdb"
>>> cmd
'sudo umount /dev/vdb'
>>> child = pexpect.spawn(cmd)
>>> child.expect(
0
>>> quit()
which is why control went ahead.
summary: |
- volume resize does not works as expected + volume resize does not works as expected for Vertica |
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → kilo-rc1 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | kilo-rc1 → 2015.1.0 |
Do not want to block Vertica BP/patchset for this resize issue, but would look into this resize issue, why is this occurring.