Skip to content
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

Only warning and error logs on azuredisk driver #68

Closed
andyzhangx opened this issue Mar 26, 2019 · 5 comments · Fixed by #69 or kubernetes-sigs/azurefile-csi-driver#46
Closed
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@andyzhangx
Copy link
Member

andyzhangx commented Mar 26, 2019

What happened:
I set as --v=5, while there are only warning and error logs on azuredisk driver, no info logs

What you expected to happen:

Only following logs are displayed even I set --v=15 for azure disk driver:

0326 07:45:09.704510       1 azuredisk.go:71] Driver: disk.csi.azure.com
I0326 07:45:09.705418       1 azuredisk.go:72] Version: v0.2.0-alpha
I0326 07:45:09.706176       1 driver.go:80] Enabling controller service capability: CREATE_DELETE_VOLUME
I0326 07:45:09.706193       1 driver.go:80] Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME
I0326 07:45:09.706199       1 driver.go:99] Enabling volume access mode: SINGLE_NODE_WRITER
I0326 07:45:09.706468       1 server.go:103] Listening for connections on address: &net.UnixAddr{Name:"//csi/csi.sock", Net:"unix"}
I0326 07:46:35.717008       1 mount_linux.go:454] `fsck` error fsck from util-linux 2.29.2
fsck.ext2: Bad magic number in super-block while trying to open /devhost/sdc
/devhost/sdc:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

E0326 07:46:35.724214       1 mount_linux.go:152] Mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t ext4 -o defaults /devhost/disk/azure/scsi1/lun0 /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-248e53b6-4f9b-11e9-bf94-000d3a04b60e/globalmount
Output: mount: wrong fs type, bad option, bad superblock on /devhost/sdc,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

I0326 07:46:35.735539       1 mount_linux.go:489] Disk "/devhost/disk/azure/scsi1/lun0" appears to be unformatted, attempting to format as type: "ext4" with options: [-F -m0 /devhost/disk/azure/scsi1/lun0]
I0326 07:46:36.963869       1 mount_linux.go:493] Disk successfully formatted (mkfs): ext4 - /devhost/disk/azure/scsi1/lun0 /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-248e53b6-4f9b-11e9-bf94-000d3a04b60e/globalmount

How to reproduce it:

Anything else we need to know?:

Environment:

  • CSI Driver version: v0.2.0-alpha
  • Kubernetes version (use kubectl version): 1.14.0
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@andyzhangx andyzhangx added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 26, 2019
@andyzhangx
Copy link
Member Author

andyzhangx commented Mar 26, 2019

cc @ashishranjan738
It looks like this PR: #48 caused this issue, logs like following logs won't be displayed in csi driver container any more.

klog.V(2).Infof("begin to create azure disk(%s) account type(%s) rg(%s) location(%s) size(%d)", diskName, skuName, resourceGroup, location, requestGiB)

if I switch to use glog, then it works well, e.g.

git checkout 01a54cea9f44edfdea1d15dd2b72bf6671527e5e
make

@andyzhangx
Copy link
Member Author

could be due to missing klog.InitFlags(nil) in main func, not sure, will try tomorrow.

@ashishranjan738
Copy link
Contributor

will have a look as well

@ashishranjan738
Copy link
Contributor

verified with the upstream image facing the same issue, but not able to reproduce it in the local system. Raised a quick fix #69

@ashishranjan738
Copy link
Contributor

could be due to missing klog.InitFlags(nil) in main func, not sure, will try tomorrow.

klog.init is present in main.go

sunpa93 pushed a commit to sunpa93/azuredisk-csi-driver that referenced this issue May 29, 2021
* Introducing the v1alpha1 types and first set of changes

* Completing the migration to use the v1alpha1 datatypes

* Updating the deepcopy

* Revert "Updating the deepcopy"

This reverts commit 056f5e9.

* Typo fix

* Handled a nil condition and added the metric for list volume and list snapshot

* Some minor fixes and review comments addressed

* updating generated files

* Merge conflicts resolved
sozercan pushed a commit to sozercan/azuredisk-csi-driver that referenced this issue Aug 16, 2021
feat: upgrade to csi 1.1.0 with expand volume support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
2 participants