search

kubernetes / mount-utils

Package mount defines an interface to mounting filesystems.
Apache License 2.0
57 stars 30 forks source link

Question: How get unsuccessful resizefs calls are logged by kubelet? #9

Closed youwalther65 closed 1 year ago

youwalther65 commented 2 years ago

I did an online PVC increase for an AWS EBS volume using in-tree provisioner which successfully increased the size of the EXT filesystem of the pod. kubelet logs this with a message which can be seen using journalctl:

# journalctl -u kubelet
...
Jun 20 09:43:28 ip-192-168-43-76.eu-west-1.compute.internal kubelet[3249]: I0620 09:43:28.598230    3249 resizefs_linux.go:70] Device /dev/xvdbr resized successfully

I figured out that this corresponds to

https://github.com/kubernetes/mount-utils/blob/master/resizefs_linux.go#L71

I have heard from some K8s users which got sporadic issues with online PVC increase where only PV and PVC got resized but FS resize failed. The Go helper function contains a log message for this as well: https://github.com/kubernetes/mount-utils/blob/master/resizefs_linux.go#L75

but the users didn't find anything in journalctl under kubelet unit. My question is where can I see unsuccessful resizefs executions to further debug those problems? Could it be just /var/log/messages or dmesg?

k8s-triage-robot commented 2 years ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/mount-utils/issues/9#issuecomment-1319977087): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues 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 with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.