testparm does not detect bad vfs objects settings
Bug #1778860 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Andreas Hasenack | ||
| samba |
Unknown
|
Unknown
|
|||
| samba (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When I upgraded to bionic, samba broke. The failure was nonobvious until I ran it in interactive mode.
testparm should be able to check I think?
anyhow, the config issue was that vfs_aio_linux had been removed, but my config still said
vfs objects = aio_linux
and testparm did not detect that as broken
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #1 |
| Changed in samba (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in ubuntu-release-notes: | |
| assignee: | nobody → Andreas Hasenack (ahasenack) |
| status: | New → In Progress |
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #2 |
| Changed in ubuntu-release-notes: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
The fact that the vfs_aio_linux module was dropped should go into the release notes, so I added a bug task for that.
Invalid vfs objects are indeed annoying to debug, because not only is testparm oblivious to such errors, smbd will also start up just fine until the share is connected to.