complete lockup #3217
Comments
|
Now I can reproduce it with just a simple ls on the problematic directory. |
|
I'm having the same problem with almost exactly the same stack trace. I have xattr=sa and acltype=off. Running kernel 3.13.0-48-generic on Ubuntu Server with ZoL 0.6.3-5. Today I upgraded my kernel to -48 from -46 but have no direct evidence this change was the culprit. I can reproduce this reliably on my system by copying a small app bundle over samba. Oddly other files don't trigger it. SMB ends up hanging and eventually the system falls over. Example stack trace from my machine:
|
|
This looks a lot like #3143 |
|
Indeed, thanks. |
|
Update to current master please, there are metadata cache limit patches now, which should address this. |
|
I doubt, that it's cache related. But I will give a try. |
|
I found out, how I can reopen the issue (via a comment..:). |
|
Most likely it isn't, at least not directly - if your ARC was/is growing uncontrollably (which these patches I'm referring to address) then you might run into a deadlock really fast, because it triggers memory reclaim. |
|
IMO this report can be closed safely. |
The very first one from yesterday in the log files:
Linux files 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
ii dkms 2.2.0.3-1.1ubuntu5.14.04+zfs9
trusty all Dynamic Kernel Module Support Frameworktrusty amd64 Native OpenZFS filesystem library for Linuxii libzfs2 0.6.3-5
ii mountall 2.53-zfs1 amd64 filesystem mounting tool
ii ubuntu-zfs 8
trusty amd64 Native ZFS filesystem metapackage for Ubuntu.trusty amd64 Native OpenZFS filesystem kernel modules for Linuxii zfs-dkms 0.6.3-5
ii zfs-doc 0.6.3-5
trusty amd64 Native OpenZFS filesystem documentation and examples.trusty amd64 Native OpenZFS management utilities for Linuxii zfs-tools 0.4.1ubuntu1-tompos-cxn7 all A collection of tools for ZFS
ii zfsutils 0.6.3-5
Starting from yesterday the machine gets completely locked up after a while.
It's reproducible it by creating 10000 directory under a directory, where inherited acl is set.
There is acltype=posixacl and xattr=sa. After xattr=on the issue is still remaining.
@dweeezil
This is the same filesystem where my previous (non-deletable) similar issue was.
Actually those files are still there.
The log files are usually empty, except the for the very first case.
When this happens processes gets stuck (I was seeing one time a cat process reading from procfs and eating 100% CPU), load goes up and the machine is going down.
IPMI console cannot be accessible.
eg.:
12560 ? R 1:01 rm -r 1 10 100 1000 10000 1001 1002 1003 1004 1005 1006 1007 1008 1009 101 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 102 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 103 10
This process is there for about 10 mins.
The text was updated successfully, but these errors were encountered: