testparm does not detect bad vfs objects settings

Bug #1778860 reported by Robert Collins on 2018-06-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Andreas Hasenack
samba (Ubuntu)

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

Andreas Hasenack (ahasenack) wrote :

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.

Changed in samba (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in ubuntu-release-notes:
assignee: nobody → Andreas Hasenack (ahasenack)
status: New → In Progress
Andreas Hasenack (ahasenack) wrote :
Changed in ubuntu-release-notes:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.