"Unable to register file system <UUID> for APD timeout notifications: Inappropriate ioctl for device" message in vSAN

Products

• VMware vSAN

Issue/Introduction

The purpose of this article is to clarify the significance of the message "Inappropriate ioctl for device".

Symptoms:

In the /var/log/vmkernel.log file of the vSAN environment, you see entries similar to:

2016-05-11T23:11:30.437Z cpu34:35283 opID=d6b83ffe)Vol3: 956: Unable to register file system ########-####-####-####-########bfac for APD timeout notifications: Inappropriate ioctl for device
2016-05-11T23:12:35.974Z cpu22:998827)Vol3: 956: Unable to register file system ########-####-####-####-########bfac for APD timeout notifications: Inappropriate ioctl for device
2016-05-11T23:13:39.196Z cpu20:999104)Vol3: 956: Unable to register file system ########-####-####-####-########bfac for APD timeout notifications: Inappropriate ioctl for device
2016-05-11T23:14:42.304Z cpu18:999402)Vol3: 956: Unable to register file system ########-####-####-####-########bfac for APD timeout notifications: Inappropriate ioctl for device
2016-05-11T23:15:45.964Z cpu0:999659)Vol3: 956: Unable to register file system ########-####-####-####-########bfac for APD timeout notifications: Inappropriate ioctl for device

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vSAN 6.x

Cause

These APD messages are logged in the vmkernel.log file when a name space is first mounted in vSAN.

Resolution

This is an expected behavior due to the underlying filesystem design in vSAN.
This message has no production impact and can be safely ignored.

Additional Information