New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input/output error when accessing PV #297
Comments
I am quite sure this issue is related to cachingmode setting as 2. disk unavailable after attach/detach a data disk on a nodeIssue details: 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
Related issues
Workaround:
Fix
|
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
|
Currently in AKS, default storage class could not be changed, I would suggest create a new storage class with |
Now that AKS is GA, do we still need to manually create a StorageClass with |
@p8952 AKS does not set cachingmode value, so it depends on your k8s version, I have make default value of cachingmode as Fix
|
FYI @jackfrancis There is a fix in acs-engine for this issue, I will leave it to you, let you decide whether set the default value of |
@ultimateboy @amanohar @weinong FYI Updating this in AKS will be a control plane concern. You can use to the acs-engine implementation as a reference. |
close the issue now since it's already resolved, let me know if you have any question. |
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.
StatefulSet:
PersistentVolumeClaim:
PersistentVolume:
Pod:
Input/Output Error:
The text was updated successfully, but these errors were encountered: