GPFS driver creates volume file on local disk when GPFS is unmounted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Qin Zhao |
Bug Description
I enable GPFS driver on one cinder volume node. After I unmount GPFS from this node, the GPFS driver can continue to handle creating volume request, so that the volume file is created on local disk, instead of GPFS NSD.
[root@zhaoqin-
Sun Oct 20 11:35:53 CDT 2013: mmumount: Unmounting file systems ...
[root@zhaoqin-
[root@zhaoqin-
[root@zhaoqin-
+------
| Property | Value |
+------
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| created_at | 2013-10-
| display_description | None |
| display_name | None |
| id | 78906f80-
| metadata | {} |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | creating |
| volume_type | None |
+------
[root@zhaoqin-
volume-
Then, I attempt to remove this volume file using cinder command, but fails.
[root@zhaoqin-
[root@zhaoqin-
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 78906f80-
+------
Changed in cinder: | |
milestone: | none → icehouse-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | icehouse-1 → 2014.1 |
Delete fails because the driver runs 'mmclone show' on the file. The question is if its worth checking if the file system is mounted on every operation.