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

UTS_RELEASE checking is depricated #17

Closed
nevenchannyy opened this issue Jun 4, 2010 · 3 comments
Closed

UTS_RELEASE checking is depricated #17

nevenchannyy opened this issue Jun 4, 2010 · 3 comments

Comments

@nevenchannyy
Copy link

./configure does't works with linux-2.6.34-gentoo release.
@nevenchannyy
Copy link
Author

behaviourism zfs # diff ./a/kernel.m4 ./b/kernel.m4
131a132,138

  elif test -r $kernelbuild/include/generated/utsrelease.h &&
          fgrep -q UTS_RELEASE $kernelbuild/include/generated/utsrelease.h; then

          kernsrcver=`(echo "#include <generated/utsrelease.h>";
                       echo "kernsrcver=UTS_RELEASE") |
                       cpp -I $kernelbuild/include |
                       grep "^kernsrcver=" | cut -d \" -f 2`

@behlendorf
Copy link
Contributor

Thanks for the bug report and patch. Currently kernels newer than 2.6.32 are not supported just yet, but we'll get there!

@behlendorf
Copy link
Contributor

Fixed by commit 61119d3, kernels up to 2.6.33 have been tested and work now.

@pyavdr pyavdr mentioned this issue Mar 28, 2012
Closed
@prometheanfire prometheanfire mentioned this issue Apr 4, 2013
Closed
@dward dward mentioned this issue Aug 26, 2013
Closed
@olw2005 olw2005 mentioned this issue Oct 17, 2013
Closed
@clefru clefru mentioned this issue Mar 2, 2014
Closed
@inevity inevity mentioned this issue Oct 15, 2014
Closed
@Mehul1313 Mehul1313 mentioned this issue Jan 14, 2015
Closed
@dswartz dswartz mentioned this issue Apr 22, 2015
Closed
@bprotopopov bprotopopov mentioned this issue Aug 11, 2015
Closed
@zp841126 zp841126 mentioned this issue Apr 22, 2016
Closed
@baukus baukus mentioned this issue Feb 7, 2017
Closed
@bprotopopov bprotopopov mentioned this issue May 10, 2017
Closed
akatrevorjay added a commit to akatrevorjay/zfs that referenced this issue Dec 16, 2017
@akatrevorjay
# This is a combination of 56 commits.
4ae6a0d 
# This is the 1st commit message:
Merge branch 'master' of https://github.com/zfsonlinux/zfs

* 'master' of https://github.com/zfsonlinux/zfs:
  Enable QAT support in zfs-dkms RPM

# This is the commit message openzfs#2:

Import 0.6.5.7-0ubuntu3

# This is the commit message openzfs#3:

gbp changes

# This is the commit message openzfs#4:

Bump ver

# This is the commit message openzfs#5:

-j9 baby

# This is the commit message openzfs#6:

Up

# This is the commit message openzfs#7:

Yup

# This is the commit message openzfs#8:

Add new module

# This is the commit message openzfs#9:

Up

# This is the commit message openzfs#10:

Up

# This is the commit message openzfs#11:

Bump

# This is the commit message openzfs#12:

Grr

# This is the commit message openzfs#13:

Yay

# This is the commit message openzfs#14:

Yay

# This is the commit message openzfs#15:

Yay

# This is the commit message openzfs#16:

Yay

# This is the commit message openzfs#17:

Yay

# This is the commit message openzfs#18:

Yay

# This is the commit message openzfs#19:

yay

# This is the commit message openzfs#20:

yay

# This is the commit message openzfs#21:

yay

# This is the commit message openzfs#22:

Update ppa script

# This is the commit message openzfs#23:

Update gbp conf with br changes

# This is the commit message openzfs#24:

Update gbp conf with br changes

# This is the commit message openzfs#25:

Bump

# This is the commit message openzfs#26:

No pristine

# This is the commit message openzfs#27:

Bump

# This is the commit message openzfs#28:

Lol whoops

# This is the commit message openzfs#29:

Fix name

# This is the commit message openzfs#30:

Fix name

# This is the commit message openzfs#31:

rebase

# This is the commit message openzfs#32:

Bump

# This is the commit message openzfs#33:

Bump

# This is the commit message openzfs#34:

Bump

# This is the commit message openzfs#35:

Bump

# This is the commit message openzfs#36:

ntrim

# This is the commit message openzfs#37:

Bump

# This is the commit message openzfs#38:

9

# This is the commit message openzfs#39:

Bump

# This is the commit message openzfs#40:

Bump

# This is the commit message openzfs#41:

Bump

# This is the commit message openzfs#42:

Revert "9"

This reverts commit de488f1.

# This is the commit message openzfs#43:

Bump

# This is the commit message openzfs#44:

Account for zconfig.sh being removed

# This is the commit message openzfs#45:

Bump

# This is the commit message openzfs#46:

Add artful

# This is the commit message openzfs#47:

Add in zed.d and zpool.d scripts

# This is the commit message openzfs#48:

Bump

# This is the commit message openzfs#49:

Bump

# This is the commit message openzfs#50:

Bump

# This is the commit message openzfs#51:

Bump

# This is the commit message openzfs#52:

ugh

# This is the commit message openzfs#53:

fix zed upgrade

# This is the commit message openzfs#54:

Bump

# This is the commit message openzfs#55:

conf file zed.d

# This is the commit message #56:

Bump
@sanjeevbagewadi sanjeevbagewadi mentioned this issue Jan 4, 2018
Closed
@BonganiMalalane BonganiMalalane mentioned this issue Aug 3, 2018
Closed
@jpfingstmann jpfingstmann mentioned this issue Mar 8, 2019
Closed
@ChessSpider ChessSpider mentioned this issue Apr 15, 2019
Closed
@twork twork mentioned this issue Jun 18, 2019
Closed
markroper added a commit to markroper/zfs that referenced this issue Feb 12, 2020
@markroper
Prevent deadlock in arc_read in Linux memory reclaim callback
6ac3449 
Using zfs with Lustre, an arc_read can trigger kernel memory allocation
that in turn leads to a memory reclaim callback and a deadlock within a
single zfs process. This change uses spl_fstrans_mark and
spl_trans_unmark to prevent the reclaim attempt and the deadlock
(https://zfsonlinux.topicbox.com/groups/zfs-devel/T4db2c705ec1804ba).
The stack trace observed is:

     #0 [ffffc9002b98adc8] __schedule at ffffffff81610f2e
     openzfs#1 [ffffc9002b98ae68] schedule at ffffffff81611558
     openzfs#2 [ffffc9002b98ae70] schedule_preempt_disabled at ffffffff8161184a
     openzfs#3 [ffffc9002b98ae78] __mutex_lock at ffffffff816131e8
     openzfs#4 [ffffc9002b98af18] arc_buf_destroy at ffffffffa0bf37d7 [zfs]
     openzfs#5 [ffffc9002b98af48] dbuf_destroy at ffffffffa0bfa6fe [zfs]
     openzfs#6 [ffffc9002b98af88] dbuf_evict_one at ffffffffa0bfaa96 [zfs]
     openzfs#7 [ffffc9002b98afa0] dbuf_rele_and_unlock at ffffffffa0bfa561 [zfs]
     openzfs#8 [ffffc9002b98b050] dbuf_rele_and_unlock at ffffffffa0bfa32b [zfs]
     openzfs#9 [ffffc9002b98b100] osd_object_delete at ffffffffa0b64ecc [osd_zfs]
    openzfs#10 [ffffc9002b98b118] lu_object_free at ffffffffa06d6a74 [obdclass]
    openzfs#11 [ffffc9002b98b178] lu_site_purge_objects at ffffffffa06d7fc1 [obdclass]
    openzfs#12 [ffffc9002b98b220] lu_cache_shrink_scan at ffffffffa06d81b8 [obdclass]
    openzfs#13 [ffffc9002b98b278] shrink_slab at ffffffff811ca9d8
    openzfs#14 [ffffc9002b98b338] shrink_node at ffffffff811cfd94
    openzfs#15 [ffffc9002b98b3b8] do_try_to_free_pages at ffffffff811cfe63
    openzfs#16 [ffffc9002b98b408] try_to_free_pages at ffffffff811d01c4
    openzfs#17 [ffffc9002b98b488] __alloc_pages_slowpath at ffffffff811be7f2
    openzfs#18 [ffffc9002b98b580] __alloc_pages_nodemask at ffffffff811bf3ed
    openzfs#19 [ffffc9002b98b5e0] new_slab at ffffffff81226304
    openzfs#20 [ffffc9002b98b638] ___slab_alloc at ffffffff812272ab
    openzfs#21 [ffffc9002b98b6f8] __slab_alloc at ffffffff8122740c
    openzfs#22 [ffffc9002b98b708] kmem_cache_alloc at ffffffff81227578
    openzfs#23 [ffffc9002b98b740] spl_kmem_cache_alloc at ffffffffa048a1fd [spl]
    openzfs#24 [ffffc9002b98b780] arc_buf_alloc_impl at ffffffffa0befba2 [zfs]
    openzfs#25 [ffffc9002b98b7b0] arc_read at ffffffffa0bf0924 [zfs]
    openzfs#26 [ffffc9002b98b858] dbuf_read at ffffffffa0bf9083 [zfs]
    openzfs#27 [ffffc9002b98b900] dmu_buf_hold_by_dnode at ffffffffa0c04869 [zfs]

Signed-off-by: Mark Roper <markroper@gmail.com>
@sneak sneak mentioned this issue Feb 27, 2020
Closed
@mattmacy mattmacy mentioned this issue Sep 22, 2020
Closed
12 tasks
@justinpryzby justinpryzby mentioned this issue Mar 16, 2021
Closed
@pgdh pgdh mentioned this issue May 28, 2021
Closed
@bu7cher bu7cher mentioned this issue Jun 11, 2021
Open
sdimitro pushed a commit to sdimitro/zfs that referenced this issue Dec 7, 2021
Fix zettacache allocation cursor on startup (openzfs#17)
7906583 
On startup, the allocation cursor for each of the buckets within the
zettacache appears to be set incorrectly. Rather than the cursor being
set to the most free slab in each bucket, we inadvertently set the
cursor to the last slab that is loaded from disk, for each bucket.

This means that on start up, if the last slab loaded for a bucket
happens to be full and at the end of the sorted slab list, a new slab
will be converted on the next allocation, rather than satisfying that
allocation from a partially allocated slab already in the bucket.

Further, it means that if that new slab is filled with new allocations
within a single checkpoint, allocation failures will result, even if the
bucket has lots of free space available.

This error is easy to make, because SlabAllocationBuckets can be in a
half-constructed state, where it's SortedSlabs don't have all the slabs,
and their last_allocated is bogus

The fix implemented here, is to no longer allow a half-constructed
SlabAllocationBuckets; instead, its new() method now takes sufficient
parameters to get it into a valid state, that accurately represents
what's on disk, before the object is returned to the caller.
@humaorong humaorong mentioned this issue Nov 4, 2022
Closed
@tongfw tongfw mentioned this issue Feb 6, 2023
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@behlendorf @nevenchannyy