CIFS VFS: No writable handle in writepages rc=-22

[vittico]

Hello

I keep seeing this message in dsmesg logs constantly. This is an Openshift 4.6 installation on Azure, everything seems to work OK, no data loss or connection issues that we can tell, just this message keeps going on, any idea what it could be?

[Mon Apr  5 01:54:53 2021] CIFS VFS: No writable handle in writepages rc=-22 
[Mon Apr  5 01:55:35 2021] CIFS VFS: No writable handle in writepages rc=-22
[Mon Apr  5 01:56:16 2021] CIFS VFS: No writable handle in writepages rc=-22
[Mon Apr  5 01:56:57 2021] CIFS VFS: No writable handle in writepages rc=-22

Other interesting lines

[Tue Apr  6 08:04:28 2021] CIFS VFS: No writable handle in writepages rc=-22
[Tue Apr  6 08:05:02 2021] FS-Cache: Duplicate cookie detected
[Tue Apr  6 08:05:02 2021] FS-Cache: O-cookie c=00000000f7ba8096 [p=0000000046187f39 fl=222 nc=0 na=1]
[Tue Apr  6 08:05:02 2021] CIFS: Attempting to mount //xxxxxxxxx.file.core.windows.net/ocp-xx-xxxxxx-dynamic-pvc-uuid-xxxxxxx-xxxxxxx-xxxxxxxx
[Tue Apr  6 08:05:02 2021] FS-Cache: O-cookie d=000000000548def0 n=0000000029b01628
[Tue Apr  6 08:05:02 2021] FS-Cache: O-key=[10] '0400020008010a0c020c'
[Tue Apr  6 08:05:02 2021] FS-Cache: N-cookie c=00000000b44104d7 [p=0000000046187f39 fl=2 nc=0 na=1]
[Tue Apr  6 08:05:02 2021] FS-Cache: N-cookie d=000000000548def0 n=000000001ba653e7
[Tue Apr  6 08:05:02 2021] FS-Cache: N-key=[10] '0400020008010a0c020c'
[Tue Apr  6 08:05:02 2021] FS-Cache: Duplicate cookie detected
[Tue Apr  6 08:05:02 2021] FS-Cache: O-cookie c=00000000f7ba8096 [p=0000000046187f39 fl=222 nc=0 na=1]
[Tue Apr  6 08:05:02 2021] FS-Cache: O-cookie d=000000000548def0 n=0000000029b01628
[Tue Apr  6 08:05:02 2021] FS-Cache: O-key=[10] '0400020008010a0c020c'
[Tue Apr  6 08:05:02 2021] FS-Cache: N-cookie c=00000000771c4595 [p=0000000046187f39 fl=2 nc=0 na=1]
[Tue Apr  6 08:05:03 2021] FS-Cache: N-cookie d=000000000548def0 n=000000000da5e939
[Tue Apr  6 08:05:03 2021] FS-Cache: N-key=[10] '0400020008010a0c020c'

spec:
  accessModes:
  - ReadWriteMany
  capacity:
    storage: 200Gi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: ************
    namespace: ******
    resourceVersion: "xxxxxxxx"
    uid:  xxxxx-xxxxxx-xxxxxx
  csi:
    driver: smb.csi.k8s.io
    nodeStageSecretRef:
      name: ****************
      namespace: *************
    volumeAttributes:
      source: //xx.xx.xx.xx/xxxxx
    volumeHandle: ************
  mountOptions:
  - dir_mode=0777
  - file_mode=0777
  - vers=3.0
  persistentVolumeReclaimPolicy: Retain
  volumeMode: Filesystem
status:
  phase: Bound

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.