# Resizing stuck on Proxmox 9.1.6 / DRBD 9.3.1

**URL:** <https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184>\
**Category:** Proxmox VE\
**Tags:** drbd\
**Created:** [March 20, 2026, 1:47pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184 "2026-03-20T13:47:04Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sayso](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sayso](https://forums.linbit.com/u/sayso)\
**Post date:** [March 20, 2026, 1:47pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/1 "2026-03-20T13:47:04Z")

</div>

Hi all, I have a brand new installation that is working well except for volume resizing. I used the Proxmox GUI to do the resize and the size incremented as expected, but `linstor volume list` and `linstor vd l` do not match and the status is stuck on resizing; there’s no change.

linstor v l

> ┊ pm-1f6a3339 ┊ r350 ┊ pve-storage ┊ 0 ┊ 1008 ┊ None ┊ 38.97 GiB ┊ Unused ┊ Resizing, UpToDate ┊ Established(1) ┊  
> ┊ pm-1f6a3339 ┊ r360 ┊ pve-storage ┊ 0 ┊ 1008 ┊ None ┊ 38.97 GiB ┊ Unused ┊ Resizing, UpToDate ┊ Established(1) ┊  
> ┊ pm-1f6a3339 ┊ t130 ┊ DfltDisklessStorPool ┊ 0 ┊ 1008 ┊ None ┊ ┊ Unused ┊ TieBreaker ┊ ┊

linstor vd l

> ┊ pm-1f6a3339 ┊ 0 ┊ 1008 ┊ 75.00 GiB ┊ ┊ resizing ┊

I’ve tried restarting linstor-satellite and linstor-controller but there’s no change.

The error log shows there ‘s a problem with the drbd command but I don’t know what to do with that!

> ERROR REPORT 69BC441B-33979-000020
> 
> ============================================================
> 
> Application: LINBIT® LINSTOR  
> Module: Satellite  
> Version: 1.33.1  
> Build ID: 95da7940d6efb6a39ea303c5f37b03478a6fab0b  
> Build time: 2025-12-22T16:04:57+00:00  
> Error time: 2026-03-19 19:35:11  
> Node: r350  
> Thread: DeviceManager
> 
> ============================================================
> 
> # Reported error:
> 
> Category: LinStorException  
> Class name: ResourceException  
> Class canonical name: com.linbit.linstor.core.devmgr.exceptions.ResourceException  
> Generated at: Method ‘adjustDrbd’, Source file ‘DrbdLayer.java’, Line #933
> 
> Error message: Failed to adjust DRBD resource pm-1f6a3339
> 
> Error context:  
> An error occurred while processing resource ‘Node: ‘r350’, Rsc: ‘pm-1f6a3339’’  
> ErrorContext:
> 
> Call backtrace:
> 
> ```auto
> Method Native Class:Line number
> adjustDrbd N com.linbit.linstor.layer.drbd.DrbdLayer:933
> processResource N com.linbit.linstor.layer.drbd.DrbdLayer:281
> lambda$processResource$1 N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:1424
> processGeneric N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:1467
> processResource N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:1420
> processResources N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:394
> dispatchResources N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:226
> dispatchResources N com.linbit.linstor.core.devmgr.DeviceManagerImpl:341
> phaseDispatchDeviceHandlers N com.linbit.linstor.core.devmgr.DeviceManagerImpl:1149
> devMgrLoop N com.linbit.linstor.core.devmgr.DeviceManagerImpl:786
> run N com.linbit.linstor.core.devmgr.DeviceManagerImpl:682
> run N java.lang.Thread:1583
> 
> ```
> 
> # Caused by:
> 
> Category: LinStorException  
> Class name: ExtCmdFailedException  
> Class canonical name: com.linbit.extproc.ExtCmdFailedException  
> Generated at: Method ‘execute’, Source file ‘DrbdAdm.java’, Line #805
> 
> Error message: The external command ‘drbdsetup’ exited with error code 5
> 
> ErrorContext:  
> Description: Execution of the external command ‘drbdsetup’ failed.  
> Cause: The external command exited with error code 5.  
> Correction: - Check whether the external program is operating properly.
> 
> - Check whether the command line is correct.  
> Contact a system administrator or a developer if the command line is no longer valid  
> for the installed version of the external program.  
> Details: The full command line executed was:  
> drbdsetup wait-connect-resource --wait-after-sb=yes --wfc-timeout=10 pm-1f6a3339
> 
> The external command sent the following output data:
> 
> The external command sent the following error information:  
> degr-wfc-timeout has to be shorter than wfc-timeout  
> degr-wfc-timeout implicitly set to wfc-timeout (10s)  
> outdated-wfc-timeout has to be shorter than degr-wfc-timeout  
> outdated-wfc-timeout implicitly set to degr-wfc-timeout (10s)
> 
> Call backtrace:
> 
> ```auto
> Method Native Class:Line number
> execute N com.linbit.linstor.layer.drbd.utils.DrbdAdm:805
> execute N com.linbit.linstor.layer.drbd.utils.DrbdAdm:788
> waitForFamily N com.linbit.linstor.layer.drbd.utils.DrbdAdm:777
> waitConnectResource N com.linbit.linstor.layer.drbd.utils.DrbdAdm:577
> resize N com.linbit.linstor.layer.drbd.utils.DrbdAdm:151
> adjustDrbd N com.linbit.linstor.layer.drbd.DrbdLayer:729
> processResource N com.linbit.linstor.layer.drbd.DrbdLayer:281
> lambda$processResource$1 N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:1424
> processGeneric N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:1467
> processResource N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:1420
> processResources N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:394
> dispatchResources N com.linbit.linstor.core.devmgr.DeviceHandlerImpl:226
> dispatchResources N com.linbit.linstor.core.devmgr.DeviceManagerImpl:341
> phaseDispatchDeviceHandlers N com.linbit.linstor.core.devmgr.DeviceManagerImpl:1149
> devMgrLoop N com.linbit.linstor.core.devmgr.DeviceManagerImpl:786
> run N com.linbit.linstor.core.devmgr.DeviceManagerImpl:682
> run N java.lang.Thread:1583
> 
> ```
> 
> END OF ERROR REPORT.

The error from the command in the error is

> degr-wfc-timeout has to be shorter than wfc-timeout  
> degr-wfc-timeout implicitly set to wfc-timeout (10s)  
> outdated-wfc-timeout has to be shorter than degr-wfc-timeout  
> outdated-wfc-timeout implicitly set to degr-wfc-timeout (10s)

Not sure what to do with that so any help appreciated!

---

<div class="post-metadata">

**Author:** ![kermat](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/kermat/32/21_2.png) [@kermat](https://forums.linbit.com/u/kermat)\
**Post date:** [March 20, 2026, 7:04pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/2 "2026-03-20T19:04:22Z")

</div>

Hello Sayso,

That’s an interesting error, since I don’t believe any of those settings have changed in DRBD for many years. Are there any user-defined settings configured on that resource?

```sh
linstor resource-group list-properties pve-rg # change resource-group name if needed

linstor resource list-properties r350 pm-1f6a3339
linstor resource list-properties r360 pm-1f6a3339
linstor resource list-properties t130 pm-1f6a3339

linstor resource-definition list-properties pm-1f6a3339

linstor volume-definition list-properties pm-1f6a3339 0

```

I see you’re on LINSTOR 1.33.1.

Can you share the versions of DRBD you have installed, as well as the `linstor-proxmox` version?

```sh
drbdadm --version
dpkg -s linstor-proxmox | grep Version

```

I did test resizing a VM disk on a cluster I had available (with a ZFS backed LINSTOR storage-pool) and everything worked as expected. Here are my software versions for completeness:

```sh
root@proxmox-0:~# drbdadm --version
DRBDADM_BUILDTAG=GIT-hash:\ 7fe34d56a7264cfc92fc5270471827bb3f7773e6\ build\ by\ @buildsystem\,\ 2026-03-17\ 06:41:38
DRBDADM_API_VERSION=2
DRBD_KERNEL_VERSION_CODE=0x090301
DRBD_KERNEL_VERSION=9.3.1
DRBDADM_VERSION_CODE=0x092200
DRBDADM_VERSION=9.34.0

root@proxmox-0:~# dpkg -s linstor-proxmox | grep Version
Version: 8.2.0-1

root@proxmox-0:~# pveversion 
pve-manager/9.1.6/71482d1833ded40a (running kernel: 6.17.13-2-pve)

root@proxmox-0:~# linstor controller version
linstor controller 1.33.1; GIT-hash: 95da7940d6efb6a39ea303c5f37b03478a6fab0b

```

---

<div class="post-metadata">

**Author:** ![sayso](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sayso](https://forums.linbit.com/u/sayso)\
**Post date:** [March 20, 2026, 8:32pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/3 "2026-03-20T20:32:11Z")

</div>

Hi kernat,

This system was built fresh just afew days ago so everything is up to date.. Heres’s the info. Thanks

> ```auto
> drbdadm --version
> DRBDADM_BUILDTAG=GIT-hash:\ 7fe34d56a7264cfc92fc5270471827bb3f7773e6\ build\ by\ @buildsystem\,\ 2026-03-17\ 06:41:38
> DRBDADM_API_VERSION=2
> DRBD_KERNEL_VERSION_CODE=0x090301
> DRBD_KERNEL_VERSION=9.3.1
> DRBDADM_VERSION_CODE=0x092200
> DRBDADM_VERSION=9.34.0
> 
> ```

> **dpkg -s linstor-proxmox | grep Version**  
> Version: 8.2.0-1

> **linstor resource-group list-properties pve-rg**  
> ┊ Key ┊ Value ┊
> 
> **linstor resource list-properties r350 pm-1f6a3339**  
> ┊ StorPoolName ┊ pve-storage ┊
> 
> **linstor resource list-properties r360 pm-1f6a3339**  
> ┊ StorPoolName ┊ pve-storage ┊
> 
> **linstor resource list-properties t130 pm-1f6a3339**  
> ┊ StorPoolName ┊ DfltDisklessStorPool ┊
> 
> **linstor resource-definition list-properties pm-1f6a3339**  
> ┊ Aux/pm/vmid ┊ 120 ┊  
> ┊ DrbdOptions/ExactSize ┊ false ┊  
> ┊ DrbdOptions/Net/allow-two-primaries ┊ yes ┊  
> ┊ DrbdOptions/Resource/quorum ┊ majority ┊  
> ┊ DrbdOptions/auto-verify-alg ┊ sha512 ┊  
> ┊ DrbdPrimarySetOn ┊ R350 ┊
> 
> **linstor volume-definition list-properties pm-1f6a3339 0**  
> ┊ DrbdCurrentGi ┊ 9F70C11F509B2F50 ┊  
> ┊ DrbdOptions/Disk/block-size ┊ 4096 ┊  
> ┊ DrbdOptions/Disk/discard-zeroes-if-aligned ┊ yes ┊  
> ┊ DrbdOptions/Disk/rs-discard-granularity ┊ 1048576 ┊  
> ┊ Linstor/Drbd/freeze-block-size ┊ True ┊  
> ┊ StorDriver/internal/AllocationGranularity ┊ 4096 ┊
> 
> **pveversion**  
> pve-manager/9.1.6/71482d1833ded40a (running kernel: 6.17.13-2-pve)
> 
> **linstor controller version**  
> linstor controller 1.33.1; GIT-hash: 95da7940d6efb6a39ea303c5f37b03478a6fab0b

---

<div class="post-metadata">

**Author:** ![kermat](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/kermat/32/21_2.png) [@kermat](https://forums.linbit.com/u/kermat)\
**Post date:** [March 20, 2026, 9:10pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/4 "2026-03-20T21:10:54Z")

</div>

If you’re using thin provisioned backing storage, then the `volume list` will show whatever is being used, while the `volume-definition list` will show you what size the volume can grow to. LINSTOR seems to be okay in that regard, but having issues with `drbdadm` on the `r350` node.

What does the output of `drbdadm status pm-1f6a3339` on the `r350` node look like? Anything different on `r360`?

Can you try running an adjust on that resource from `r350` to see if that produces the same error LINSTOR is getting back?

```sh
drbdadm adjust pm-1f6a3339

```

Or even a `resize all`?

```sh
drbdadm resize all

```

---

<div class="post-metadata">

**Author:** ![sayso](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sayso](https://forums.linbit.com/u/sayso)\
**Post date:** [March 20, 2026, 10:59pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/5 "2026-03-20T22:59:36Z")

</div>

Here’s the output from `volume-definition list` on r350…

> root@r350:~# **drbdadm status pm-1f6a3339**  
> pm-1f6a3339 role:Secondary  
> disk:UpToDate open:no  
> pve connection:Connecting  
> r360 role:Secondary  
> peer-disk:UpToDate

and r360…

> root@r360:~# **drbdadm status pm-1f6a3339**  
> pm-1f6a3339 role:Secondary  
> disk:Inconsistent open:no  
> pve connection:Connecting  
> r350 role:Secondary  
> replication:SyncTarget peer-disk:UpToDate done:41.49

Here’s the volume-definition list

> root@r350:~# **linstor volume-definition list**  
> ┊ ResourceName ┊ VolumeNr ┊ VolumeMinor ┊ Size ┊ Gross ┊ State ┊  
> ┊ pm-1f6a3339 ┊ 0 ┊ 1008 ┊ 75.00 GiB ┊ ┊ resizing ┊  
> ┊ pm-4922ade0 ┊ 0 ┊ 1001 ┊ 66.00 GiB ┊ ┊ resizing ┊

`drbdadm resize all` completes on r350 but hangs on r360

---

<div class="post-metadata">

**Author:** ![sayso](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sayso](https://forums.linbit.com/u/sayso)\
**Post date:** [March 21, 2026, 9:47pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/6 "2026-03-21T21:47:29Z")

</div>

Update!

Either `drbdadm adjust pm-1f6a3339` and/or `drbdadm resize all` made a difference. However `linstor v l` and `linstor vd l` don’t agree on the size, I did expand the partition in the VM and have added usable space…

> **linstor volume-definition list**  
> ┊ pm-1f6a3339 ┊ 0 ┊ 1008 ┊ 75.00 GiB ┊ ┊ ok ┊

> **linstor volume list**  
> ┊ pm-1f6a3339 ┊ r350 ┊ pve-storage ┊ 0 ┊ 1008 ┊ /dev/drbd1008 ┊ 39.53 GiB ┊ InUse ┊ UpToDate ┊ Established(1) ┊  
> ┊ pm-1f6a3339 ┊ r360 ┊ pve-storage ┊ 0 ┊ 1008 ┊ /dev/drbd1008 ┊ 39.53 GiB ┊ Unused ┊ UpToDate ┊ Established(1) ┊  
> ┊ pm-1f6a3339 ┊ t130 ┊ DfltDisklessStorPool ┊ 0 ┊ 1008 ┊ /dev/drbd1008 ┊ ┊ Unused ┊ TieBreaker ┊ ┊

---

<div class="post-metadata">

**Author:** ![kermat](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/kermat/32/21_2.png) [@kermat](https://forums.linbit.com/u/kermat)\
**Post date:** [April 6, 2026, 3:33pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/7 "2026-04-06T15:33:32Z")

</div>

If you’re using thin-provisioned backing storage for LINSTOR’s storage-pools, the difference between `volume` and `volume-definition` is expected:

> [@kermat](#):
>
> If you’re using thin provisioned backing storage, then the `volume list` will show whatever is being used, while the `volume-definition list` will show you what size the volume can grow to.

---

<div class="post-metadata">

**Author:** ![sayso](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@sayso](https://forums.linbit.com/u/sayso)\
**Post date:** [April 6, 2026, 6:15pm UTC](https://forums.linbit.com/t/resizing-stuck-on-proxmox-9-1-6-drbd-9-3-1/1184/8 "2026-04-06T18:15:33Z")

</div>

Thanks. I figured that’s what’s going on. Resizing seems to work now bit it takea forever to complete