Large kmem_alloc(74472, 0x1000) #8491
Comments
|
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
|
FWIW, I had this reproduce on my Debian box with |
|
Sadly I don't think the devs are going to care to work on fixing 0.7.x. I suggest reproducing on 0.8.4, 0.8.5-staging, or preferably 2.0-rc2 or master. |
|
Still get these with 0.8.4 |
|
@luke-jr is this still on a power9 system? Can you check the page size. |
|
I believe both of us are reporting from POWER9 machines. Debian prefers to use 64KiB pages thereon: |
|
Yes, as my kernel version hints, it's with 64k pages. ;) |
|
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
|
This warning is caused by the 64k page size and it has not yet been fixed. |
behlendorf
added
the
good first issue
behlendorf
added
the
Type: Architecture
|
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
behlendorf
added
Bot: Not Stale
|
Same issue, similar hardware to Luke, zfs cloned and built manually as of commit: b15ab50 Pagesize is 64K: getconf PAGESIZE Debian version is bookworm. [1384381.922929] CPU: 112 PID: 360687 Comm: arc_prune Tainted: P W O 6.1.0-5-powerpc64le #1 Debian 6.1.12-1 —this machine is a non-production Talos II w/ only 128GB RAM installed. Therefore, I would be willing to run tests. I would prefer not to lose any data on the array, but theoretically I wouldn't yell at anybody if I did esp. if it led to a correct "fix" even if the fix is to change my spl_kmem_alloc_max to something large enough, or to simply silence the warning. |
The kmem allocation in zfs_prune_aliases() will trigger a large allocation warning on systems with 64K pages. Resolve this by switching to vmem_alloc() which internally uses kvmalloc() so the right allocator will be used based on the allocation size. Signed-off-by: Brian Behlendorf <[email protected]> Issue openzfs#8491
The kmem allocation in zfs_prune_aliases() will trigger a large allocation warning on systems with 64K pages. Resolve this by switching to vmem_alloc() which internally uses kvmalloc() so the right allocator will be used based on the allocation size. Signed-off-by: Brian Behlendorf <[email protected]> Issue openzfs#8491
The kmem allocation in zfs_prune_aliases() will trigger a large allocation warning on systems with 64K pages. Resolve this by switching to vmem_alloc() which internally uses kvmalloc() so the right allocator will be used based on the allocation size. Reviewed-by: Richard Yao <[email protected]> Reviewed-by: Tino Reichardt <[email protected]> Reviewed-by: Brian Atkinson <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes openzfs#8491 Closes openzfs#14694
The kmem allocation in zfs_prune_aliases() will trigger a large allocation warning on systems with 64K pages. Resolve this by switching to vmem_alloc() which internally uses kvmalloc() so the right allocator will be used based on the allocation size. Reviewed-by: Richard Yao <[email protected]> Reviewed-by: Tino Reichardt <[email protected]> Reviewed-by: Brian Atkinson <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes openzfs#8491 Closes openzfs#14694
The kmem allocation in zfs_prune_aliases() will trigger a large allocation warning on systems with 64K pages. Resolve this by switching to vmem_alloc() which internally uses kvmalloc() so the right allocator will be used based on the allocation size. Reviewed-by: Richard Yao <[email protected]> Reviewed-by: Tino Reichardt <[email protected]> Reviewed-by: Brian Atkinson <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes #8491 Closes #14694
The kmem allocation in zfs_prune_aliases() will trigger a large allocation warning on systems with 64K pages. Resolve this by switching to vmem_alloc() which internally uses kvmalloc() so the right allocator will be used based on the allocation size. Reviewed-by: Richard Yao <[email protected]> Reviewed-by: Tino Reichardt <[email protected]> Reviewed-by: Brian Atkinson <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes openzfs#8491 Closes openzfs#14694
System information
(ZFS/SPL are built-in, so I'm not 100% sure of the version)
Describe the problem you're observing
dmesg shows a request to report a bug. I haven't noticed any symptoms.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: