Loading...
Loading...
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 21bc3357-bed6-7e9a-a4a9-3464a990bfac for APD timeout notifications: Inappropriate ioctl for device2016-05-11T23:12:35.974Z cpu22:998827)Vol3: 956: Unable to register file system 21bc3357-bed6-7e9a-a4a9-3464a990bfac for APD timeout notifications: Inappropriate ioctl for device2016-05-11T23:13:39.196Z cpu20:999104)Vol3: 956: Unable to register file system 21bc3357-bed6-7e9a-a4a9-3464a990bfac for APD timeout notifications: Inappropriate ioctl for device2016-05-11T23:14:42.304Z cpu18:999402)Vol3: 956: Unable to register file system 21bc3357-bed6-7e9a-a4a9-3464a990bfac for APD timeout notifications: Inappropriate ioctl for device2016-05-11T23:15:45.964Z cpu0:999659)Vol3: 956: Unable to register file system 21bc3357-bed6-7e9a-a4a9-3464a990bfac 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.
The purpose of this article is to clarify the significance of the message "Inappropriate ioctl for device".
These APD messages are logged in the vmkernel.log file when a name space is first mounted in vSAN.
This is an expected behavior due to the underlying filesystem design in vSAN.This message has no production impact and can be safely ignored.
可以放心地忽略 vSAN APD 消息：无法为 APD 超时通知注册文件系统 <UUID>: 设备的 ioctl 不正确 (Unable to register file system <UUID> for APD timeout notifications: Inappropriate ioctl for device)無視してもかまわない vSAN APD メッセージ：APD タイムアウト通知のファイル システム <UUID> を登録できません：デバイスに対する不適切な ioctl (Unable to register file system <UUID> for APD timeout notifications: Inappropriate ioctl for device)
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.