Cannot find a free bint for tdisk oraclevm_test1 size 4096

38 views
Skip to first unread message

Sergey Ganchuk

unread,
Sep 21, 2019, 9:51:28 AM9/21/19
to QUADStor Storage Virtualization
Hi everybody.
My quadstor has ran into this problem:
Sep 21 13:12:09 quadstor1 kernel: WARN: bdev_alloc_for_pgdata:5014 Cannot find a free bint for tdisk oraclevm_test1 size 4096
Sep 21 13:12:09 quadstor1 kernel: WARN: bdev_alloc_block:5122 Cannot find a free bint for size 4096
Sep 21 13:12:09 quadstor1 kernel: WARN: bdev_alloc_block:5161 Group Default free 1571160747520
Sep 21 13:12:09 quadstor1 kernel: WARN: pgdata_alloc_blocks:5509 bdev alloc block failed for size 4096
Sep 21 13:12:12 quadstor1 kernel: WARN: scan_write_data:5719 pgdata alloc blocks failed for size 4096
Sep 21 13:12:12 quadstor1 kernel: WARN: __tdisk_cmd_write:6277 scan write data failed for lba 5451 transfer length 1
Sep 21 13:12:12 quadstor1 kernel: WARN: __tdisk_cmd_write:6449 write failed for lba 5451 transfer length 1 cw 1 cmd 89 sent ctio 0
Sep 21 13:12:12 quadstor1 kernel: WARN: bdev_alloc_for_pgdata:5014 Cannot find a free bint for tdisk oraclevm_test1 size 4096
Sep 21 13:12:12 quadstor1 kernel: WARN: bdev_alloc_block:5122 Cannot find a free bint for size 4096
Sep 21 13:12:12 quadstor1 kernel: WARN: bdev_alloc_block:5161 Group Default free 1571160747520
Sep 21 13:12:12 quadstor1 kernel: WARN: pgdata_alloc_blocks:5509 bdev alloc block failed for size 4096
Sep 21 13:12:15 quadstor1 kernel: WARN: scan_write_data:5719 pgdata alloc blocks failed for size 4096
Sep 21 13:12:15 quadstor1 kernel: WARN: __tdisk_cmd_write:6277 scan write data failed for lba 5451 transfer length 1
Sep 21 13:12:15 quadstor1 kernel: WARN: __tdisk_cmd_write:6449 write failed for lba 5451 transfer length 1 cw 1 cmd 89 sent ctio 0
Sep 21 13:12:15 quadstor1 kernel: WARN: bdev_alloc_for_pgdata:5014 Cannot find a free bint for tdisk oraclevm_test1 size 4096
Sep 21 13:12:15 quadstor1 kernel: WARN: bdev_alloc_block:5122 Cannot find a free bint for size 4096
Sep 21 13:12:15 quadstor1 kernel: WARN: bdev_alloc_block:5161 Group Default free 1571160747520
Sep 21 13:12:15 quadstor1 kernel: WARN: pgdata_alloc_blocks:5509 bdev alloc block failed for size 4096
Sep 21 13:12:18 quadstor1 kernel: WARN: scan_write_data:5719 pgdata alloc blocks failed for size 4096
Sep 21 13:12:18 quadstor1 kernel: WARN: __tdisk_cmd_write:6277 scan write data failed for lba 5451 transfer length 1
Sep 21 13:12:18 quadstor1 kernel: WARN: __tdisk_cmd_write:6449 write failed for lba 5451 transfer length 1 cw 1 cmd 89 sent ctio 0
Sep 21 13:12:18 quadstor1 kernel: WARN: bdev_alloc_for_pgdata:5014 Cannot find a free bint for tdisk oraclevm_test1 size 4096
Sep 21 13:12:18 quadstor1 kernel: WARN: bdev_alloc_block:5122 Cannot find a free bint for size 4096
Sep 21 13:12:18 quadstor1 kernel: WARN: bdev_alloc_block:5161 Group Default free 1571160747520
Sep 21 13:12:18 quadstor1 kernel: WARN: pgdata_alloc_blocks:5509 bdev alloc block failed for size 4096
Sep 21 13:12:21 quadstor1 kernel: WARN: scan_write_data:5719 pgdata alloc blocks failed for size 4096
Sep 21 13:12:21 quadstor1 kernel: WARN: __tdisk_cmd_write:6277 scan write data failed for lba 5451 transfer length 1
Sep 21 13:12:21 quadstor1 kernel: WARN: __tdisk_cmd_write:6449 write failed for lba 5451 transfer length 1 cw 1 cmd 89 sent ctio 0

I have one pool 
IDVendorModelSerial NumberNameSizeUsedStatus
1AVAGOMR9361-8i00791e94e425e81723e0702a0eb00506sda48.673 TB8.315 TBD
2AVAGOMR9361-8i00309653e753e81723e0702a0eb00506sdb8.730 TB8.374 TB
3AVAGOMR9361-8i00680c69666c0e1823e0702a0eb00506sdc8.730 TB8.375 TB
4AVAGOMR9361-8i00909892edbce81723e0702a0eb00506sdd6.984 TB6.625 TB
Pool Disk Statistics
Total Size:33.118 TB
Used Size:31.689 TB
VDisk Usage:31.603 TB
Deduped Size:23.58 GB
Uncompressed Size:31.580 TB
Compressed Size:0.00 KB
Compression Hits:0.00 KB
Dedupe Ratio:1.001

And two vdisks:
oraclevm_test1Default6e5bef205312d47d600479ed1d65c61816384 GBEModifyView
oraclevm_test2Default6ec81be79e5006c77d6f0f67d0019ff416384 GBEModifyView

After restart of the server it works for a while, but then fails again.

PS. What happened with the site?

QUADStor Support

unread,
Sep 21, 2019, 9:55:09 AM9/21/19
to quadstor-virt
The writes are failing because the available free physical space is low. Since these are VMs maybe an unmap will help. 

The site is experiencing problems. We will check why

--
You received this message because you are subscribed to the Google Groups "QUADStor Storage Virtualization" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quadstor-vir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quadstor-virt/ec3531e6-31cd-456b-9f17-4e5a5b2597af%40googlegroups.com.

QUADStor Support

unread,
Sep 21, 2019, 10:02:18 AM9/21/19
to quadstor-virt
Site is fine now.

Regarding UNMAP (if ESXi) please refer to 

Reply all
Reply to author
Forward
0 new messages