The failure occurs as a result of a new allocation check (for kvmalloc_node)
that was added between 5.9 and 5.15+
https://github.com/torvalds/linux/commit/7661809d493b426e979f39ab512e3adf41fbcc69
It also requires two conditions:
1. The drive presents an optimal IO size > 0 (checked at
/sys/block/{drive}/queue/optimal_io_size)
2. The drive is large. This will vary depending on sectors and the optimal io
size, but assuming 512b sectors, and optimal io size 4096, drives larger than
2TiB would fail.
Should be fixed as part of this upstream patchset:
https://lore.kernel.org/linux-bcache/20230307134852.8288-1-mingzhe....@easystack.cn/T/#u
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016040
Title:
Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB
storage fails with "cannot allocate memory" error
Status in linux package in Ubuntu:
Confirmed
Bug description:
# make-bcache -B /dev/nvme4n1
UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141
Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f
version: 1
block_size: 1
data_offset: 16
kern.log:
Apr 12 18:21:56 ... kernel: [ 723.854659] bcache: register_bdev() error
nvme4n1: cannot allocate memory
Apr 12 18:21:56 ... kernel: [ 723.854662] bcache: register_bdev_worker()
error /dev/nvme4n1: fail to register backing device
Same error message is mentioned in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the
suggested configuration change does not fix the issue:
# nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format"
[3:0] : 0x3 Current LBA Format Selected
LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative
Performance: 0 Best
LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative
Performance: 0 Best
LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative
Performance: 0 Best
LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative
Performance: 0 Best (in use)
LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative
Performance: 0 Best
LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative
Performance: 0 Best
Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected:
# make-bcache -B /dev/nvme2n1
UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0
Set UUID: af6b190f-a57e-4f2b-926e-904a95268390
version: 1
block_size: 8
data_offset: 16
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
...
nvme2n1 259:1 0 372.6G 0 disk
└─bcache0 252:0 0 372.6G 0 disk
...
kern.log:
Apr 12 18:47:33 ... kernel: [ 2261.135332] bcache: register_bdev() registered
backing device nvme2n1
Kernel versions tested:
5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
5.15.0-69-generic #76-Ubuntu SMP
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Apr 12 18:10 seq
crw-rw---- 1 root audio 116, 33 Apr 12 18:10 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 22.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R7525
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic
root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-38-generic N/A
linux-backports-modules-5.19.0-38-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.12
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.19.0-38-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/25/2022
dmi.bios.release: 2.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.2
dmi.board.name: 03WYW4
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525:
dmi.product.family: PowerEdge
dmi.product.name: PowerEdge R7525
dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
