-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
case insensitivity and kernel release 4.7+ #5507
Comments
Can you test whether this also occurs with kernels that use CFS (stock) cpu scheduler ? |
Great, I'll test that straightaway. If that fixes the issue it is highly likely that the CK patches are not to blame. |
On Wednesday December 21 2016 03:53:04 LOLi wrote:
@RJVB this should be fixed by #5141 (_Linux 4.7: fix deadlock during lookup on case-insensitive_). You can find a patch for 0.6.5.8 in the comments.
I can confirm now: that patch fixed my issue on 4.8.15 , with the ck8 patch still in place.
FWIW: Con Kolivas has been working on a new scheduler ("muqss") that should be a bit more appropriate for normal desktop use, esp. if you often run applications at background priority levels (http://www.phoronix.com/scan.php?page=news_item&px=MuQSS-First-Major-Release)
|
@RJVB as i see the issue is already solved. Feel free to reopen if it's not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am experiencing an issue with a case-insensitive dataset running 0.6.5.8 built for Ubuntu 14.04 (see ppa:rjvbertin/misc) under mainstream kernels 4.7.2 and 4.8.15 built with the ConKolivas patches.
Any process trying to access a mounted case-insensitive dataset hangs, and that includes zfs.mount when mounting a case-sensitive child of the case-insensitive dataset. With hanging I mean that the process is completely unresponsive to signals and interrupts though it does not show up as a zombie:
For instance:
The dataset properties:
Running kernel 4.5.7 with the same patches I do not have this issue, suggestion that it is related to the modifications made to enable ZFS on 4.7+ kernels.
The text was updated successfully, but these errors were encountered: