"volume" is apparently in use by the system; will not make a filesystem here! about synology-csi HOT 5 CLOSED

@chihyuwu

1. Mount doesn't show any mounted volumes, but fdisk -l shows the availability.
2. Yes.
3. https://github.com/SynologyOpenSource/synology-csi/blob/main/deploy/helm/templates/storageclass.yaml

Edit: 1) any other beside nvme0n1 and tmpfs/overlay/etc for k8s workloads.

from synology-csi.

Hi @salzig,
Could you provide more information for us to investigate? Thank you.

1. output of mount or mount | grep sda on your machine
2. Is this LUN new created by CSI?
3. The cofig of the StorageClass synology-csi-retain

from synology-csi.

@chihyuwu Looks like a Volume size of 320GB ends up in a timeout. Using a 30GB it worked just fine. Monitoring the Synology SAN Manager I can see that the 320GB thin provisioned volume gets utilised ("used") gigabyte by gigabyte. At around ~80GB k8s fails with a timeout. Looks like the ext4 (default) fs creation takes to long.

from synology-csi.

Hi @salzig,
The timeout issue of formatting filesystem was resolved in PR #49.
Please pull the latest CSI: synology/synology-csi:latest (note that version 1.1.2 doesn't include this fix),
and configure your StorageClass with additional parameter formatOptions as shown below to skip discarding blocks:

For ext4 fs:

parameters:
  fsType: 'ext4'
  formatOptions: "-E nodiscard"
  protocol: 'iscsi'

For btrfs fs:

parameters:
  fsType: 'btrfs'
  formatOptions: "--nodiscard"
  protocol: 'iscsi'

from synology-csi.

Sorry for the late response: Yes, this works. Meanwhile I migrated away from iSCSI, as this prevents auto updates on symbology.

from synology-csi.