swift mount - nobarrier not available with xfs in the modern kernels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
Medium
|
Radosław Piliszek | ||
Rocky |
Fix Released
|
Medium
|
Radosław Piliszek | ||
Stein |
Fix Released
|
Medium
|
Radosław Piliszek | ||
Train |
Fix Released
|
Medium
|
Radosław Piliszek | ||
Ussuri |
Fix Released
|
Medium
|
Radosław Piliszek |
Bug Description
I think I figured out the issue while I was investigating while writing this, but there is still an issue.
It looks like the options for mounting, configured here:
https:/
has the "nobarrier" option. This option is deprecated, and actually removed in the latest kernel (4.19.0-
https:/
I left my original explanation I was going to submit below, in case it helps to see the results of the problem (it obviously didn't have anything to do with partition 2 not existing).
Eric
I wasn't sure how to word the summary, but essentially, it looks like a recent change to the kolla_toolbox (maybe?) automatically assumes that partition 2 will be assigned as a journal partition.
We have single partitions for every Swift object storage drive, labeled as KOLLA_SWIFT_DATA (as described here: https:/
This worked perfectly until I tried the Kolla-Ansible and Kolla release for 7.0.0.
We have failures during deploy in the task "[swift : Mounting Swift disks]".
Below (end of this message) are two log entries, the first is when it succeeded on October 15, 2018, the second failed today (October 26, 2018).
Note that this is the output from "parted" on the failed node which shows the formatted partition (but only a single partition):
Model: ATA HGST HUH721010AL (scsi)
Disk /dev/sda: 10.0TB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 10.0TB 10.0TB xfs KOLLA_SWIFT_DATA
Did something change that requires a second partition for the journal?
Eric
Succeeded:
ok: [compute001] => (item={u'fs_uuid': u'5266599c-
"changed": false,
"dump": "0",
"fstab": "/etc/fstab",
"fstype": "xfs",
"invocation": {
"boot": true,
"dump": null,
"name": "/srv/node/d0",
"opts": "noatime,
"path": "/srv/node/d0",
"src": "UUID=5266599c-
}
},
"item": {
"device": "/dev/sda",
"fs_label": "d0",
"fs_uuid": "5266599c-
"journal": "/dev/sda2",
},
"name": "/srv/node/d0",
"opts": "noatime,
"passno": "0",
"src": "UUID=5266599c-
}
Failed:
failed: [compute001](item={
u'fs_uuid': u'1548d474-
u'journal_device': u'/dev/sda',
u'journal': u'/dev/sda2',
u'partition': u'/dev/sda1',
u'partition_num': u'1',
u'journal_num': 2,
u'fs_label': u'd0',
u'device': u'/dev/sda',
u'partition_
u'external_
})=>{
"changed": false,
"item": {
"device": "/dev/sda",
"external_
"fs_label": "d0",
"fs_uuid": "1548d474-
"journal": "/dev/sda2",
"journal_device": "/dev/sda",
"journal_num": 2,
"partition": "/dev/sda1",
"partition_
"partition_num": "1"
},
"msg": "Error mounting /srv/node/d0: mount: wrong fs type, bad option, bad superblock on /dev/sda1,\n missing codepage or helper program, or other error\n\n In some cases useful info is found in syslog - try\n dmesg | tail or so.\n"
}
Changed in kolla-ansible: | |
status: | New → Triaged |
summary: |
- Kolla Ansible 7.0.0 release requires two partitions for Swift object - disks + swift mount - nobarrier not available with xfs |
Affects debian buster which is a supported platform (train), and will affect centos 8 (ussuri).