Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Large kmem_alloc(76800, 0x0) #8934

Closed
m-kozlowski opened this issue Jun 19, 2019 · 1 comment · Fixed by #9011
Closed

Large kmem_alloc(76800, 0x0) #8934

m-kozlowski opened this issue Jun 19, 2019 · 1 comment · Fixed by #9011
Labels
good first issue Indicates a good issue for first-time contributors Type: Defect Incorrect behavior (e.g. crash, hang)

Comments

@m-kozlowski
Copy link

m-kozlowski commented Jun 19, 2019 •
edited
Loading

System information

Type Version/Name
Distribution Name Ubuntu
Distribution Version 19.04
Linux Kernel 5.1.4-mpk
Architecture x86_64
ZFS Version 0.8.1-1
SPL Version 0.8.1-1

Describe the problem you're observing

[   17.943690] Large kmem_alloc(76800, 0x0), please file an issue at:
               https://github.com/zfsonlinux/zfs/issues/new
[   17.943697] CPU: 2 PID: 1269 Comm: zpool Tainted: P           O      5.1.4-mpk #1
[   17.943699] Hardware name: ASUSTeK COMPUTER INC. P10S-I Series/P10S-I Series, BIOS 4401 03/05/2018
[   17.943700] Call Trace:
[   17.943711]  dump_stack+0x46/0x60
[   17.943721]  spl_kmem_alloc.cold.2+0x16/0x1b [spl]
[   17.943785]  vdev_indirect_births_open+0xa5/0xf0 [zfs]
[   17.943839]  spa_remove_init+0xbc/0x1e0 [zfs]
[   17.943897]  spa_load+0xbf/0x13e0 [zfs]
[   17.943905]  ? zpool_get_load_policy+0x72/0x1c0 [zcommon]
[   17.943962]  spa_tryimport+0x116/0x550 [zfs]
[   17.944007]  zfs_ioc_pool_tryimport+0x61/0xc0 [zfs]
[   17.944051]  zfsdev_ioctl+0x6cf/0x8c0 [zfs]
[   17.944058]  ? mem_cgroup_throttle_swaprate+0x17/0x110
[   17.944064]  ? __handle_mm_fault+0xf90/0x12d0
[   17.944070]  do_vfs_ioctl+0xa5/0x620
[   17.944075]  ksys_ioctl+0x60/0x90
[   17.944079]  __x64_sys_ioctl+0x16/0x20
[   17.944083]  do_syscall_64+0x4f/0x100
[   17.944090]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   17.944094] RIP: 0033:0x7fa3c8095417
[   17.944098] Code: 00 00 90 48 8b 05 79 0a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 49 0a 0d 00 f7 d8 64 89 01 48
[   17.944100] RSP: 002b:00007ffe9fefc9b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[   17.944104] RAX: ffffffffffffffda RBX: 00007ffe9fefc9d0 RCX: 00007fa3c8095417
[   17.944106] RDX: 00007ffe9fefc9d0 RSI: 0000000000005a06 RDI: 0000000000000003
[   17.944107] RBP: 00007ffe9fefffa0 R08: 00007fa3c7428010 R09: 0000000000000000
[   17.944109] R10: 0000000000000022 R11: 0000000000000246 R12: 0000561ee78ce4f0
[   17.944110] R13: 0000561ee78cff80 R14: 0000561ee78cfec0 R15: 0000000000000000

I'm not experiencing any issues, except from message above.

Describe how to reproduce the problem

It seems to occur every pool import. One of two pools on the system.
I believe issue appeared after removing mirrored vdevs from pool (yeah, i've been playing with new toys from 0.8.0 release;)

  pool: storage
 state: ONLINE
  scan: scrub repaired 0B in 0 days 17:09:25 with 0 errors on Wed Jun 19 13:38:51 2019
remove: Removal of vdev 2 copied 880G in 2h17m, completed on Tue Jun 18 10:22:11 2019
    8.44M memory used for removed device mappings
config:

        NAME                                          STATE     READ WRITE CKSUM
        storage                                       ONLINE       0     0     0
          mirror-0                                    ONLINE       0     0     0
            ata-WDC_WD100EFAX-68LHPN0_2YHV69DD        ONLINE       0     0     0
            ata-WDC_WD100EFAX-68LHPN0_2YHV9UGD        ONLINE       0     0     0
          mirror-4                                    ONLINE       0     0     0
            ata-WDC_WD60EFAX-68SHWN0_WD-WX11D1951E89  ONLINE       0     0     0
            ata-WDC_WD60EFAX-68SHWN0_WD-WX31D2992CYT  ONLINE       0     0     0
          mirror-5                                    ONLINE       0     0     0
            ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHL90A  ONLINE       0     0     0
            ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N2VXDJSN  ONLINE       0     0     0
          mirror-6                                    ONLINE       0     0     0
            ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHL28R  ONLINE       0     0     0
            ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4KVC33A  ONLINE       0     0     0

errors: No known data errors

2019-06-17.20:04:33 zpool add storage mirror ata-WDC_WD60EFAX-68SHWN0_WD-WX31D2992CYT ata-WDC_WD60EFAX-68SHWN0_WD-WX11D1951E89
2019-06-17.20:30:10 zpool remove storage mirror-3
2019-06-17.21:32:41 zpool add storage mirror ata-WDC_WD60EFAX-68SHWN0_WD-WX11D1951E89 ata-WDC_WD60EFAX-68SHWN0_WD-WX31D2992CYT
...
2019-06-18.00:46:13 zpool remove storage mirror-1
2019-06-18.08:05:15 zpool remove storage mirror-2
2019-06-18.19:40:49 zpool scrub storage
2019-06-18.20:15:07 zpool add storage -o ashift=12 mirror ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHL90A ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N2VXDJSN mirror ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N2ZHL28R ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4KVC33A
2019-06-18.20:29:43 zpool scrub storage
@behlendorf behlendorf added good first issue Indicates a good issue for first-time contributors Type: Defect Incorrect behavior (e.g. crash, hang) labels Jun 20, 2019
@behlendorf
Copy link
Contributor

Thanks for filing this, the large allocation warning shouldn't cause any problems for the pool.

nmattis added a commit to nmattis/zfs that referenced this issue Jul 9, 2019
@nmattis
Fixes: openzfs#8934 Large kmem_alloc
197ac61 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
@nmattis nmattis mentioned this issue Jul 10, 2019
Merged
12 tasks
behlendorf pushed a commit that referenced this issue Jul 10, 2019
@nmattis @behlendorf
Fixes: #8934 Large kmem_alloc
d230a65 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes #8934
Closes #9011
TulsiJain pushed a commit to TulsiJain/zfs that referenced this issue Jul 20, 2019
@nmattis
Fixes: openzfs#8934 Large kmem_alloc
22a0b64 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
Closes openzfs#9011
TulsiJain pushed a commit to TulsiJain/zfs that referenced this issue Jul 20, 2019
@nmattis
Fixes: openzfs#8934 Large kmem_alloc
0d12719 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
Closes openzfs#9011
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Aug 13, 2019
@nmattis @tonyhutter
Fixes: openzfs#8934 Large kmem_alloc
4b2d3b3 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
Closes openzfs#9011
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Aug 22, 2019
@nmattis @tonyhutter
Fixes: openzfs#8934 Large kmem_alloc
10dc94e 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
Closes openzfs#9011
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Aug 23, 2019
@nmattis @tonyhutter
Fixes: openzfs#8934 Large kmem_alloc
3cf883f 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
Closes openzfs#9011
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Sep 17, 2019
@nmattis @tonyhutter
Fixes: openzfs#8934 Large kmem_alloc
3da423f 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
Closes openzfs#9011
tonyhutter pushed a commit to tonyhutter/zfs that referenced this issue Sep 18, 2019
@nmattis @tonyhutter
Fixes: openzfs#8934 Large kmem_alloc
9349981 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes openzfs#8934
Closes openzfs#9011
tonyhutter pushed a commit that referenced this issue Sep 26, 2019
@nmattis @tonyhutter
Fixes: #8934 Large kmem_alloc
cf966cb 
Large allocation over the spl_kmem_alloc_warn value was being performed.
Switched to vmem_alloc interface as specified for large allocations.
Changed the subsequent frees to match.

Reviewed-by: Tom Caputi <tcaputi@datto.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: nmattis <nickm970@gmail.com>
Closes #8934
Closes #9011
@problame problame mentioned this issue Sep 25, 2020
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Indicates a good issue for first-time contributors Type: Defect Incorrect behavior (e.g. crash, hang)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes: #8934 Large kmem_alloc nmattis/zfs
2 participants
@behlendorf @m-kozlowski