Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Input/output error when accessing PV #297
Since around 11:45 UTC AKS in Western Europe seems to have been having issues accessing PVs from inside pods.
I've deleted the STS/POD/PVC/PV as well as the underlying Azure Disk and re-created them but experience the same behvaiour.
PVs appear to work at first but stop responding after a short while.
I am quite sure this issue is related to cachingmode setting as
2. disk unavailable after attach/detach a data disk on a node
From k8s v1.7, default host cache setting changed from
In my testing on Ubuntu 16.04 D2_V2 VM, when attaching the 6th data disk will cause device name change on agent node, e.g. following lun0 disk should be
Thanks @andyzhangx, I'll give that a go.
Just one thing to note, I am not currently defining a StorageClass but rather relying on the default storage class. If there are issues with
@p8952 AKS does not set cachingmode value, so it depends on your k8s version, I have make default value of cachingmode as