-
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
Hang on access to zfs filesystem since 0.6.5.5 #5147
Comments
Are you using Linux 4.7+? |
Mmm most probably yes I updated zfs at the same time as going to 4.7.0 and error is still happening on 4.7.4. I'll follow the other thread, sorry for duplicate didn't relate to kernel version. |
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Oct 19, 2016
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
stiell
pushed a commit
to stiell/zfs
that referenced
this issue
Oct 21, 2016
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Oct 29, 2016
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Jan 20, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Feb 2, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes openzfs#5124 Closes openzfs#5141 Closes openzfs#5147 Closes openzfs#5148 Requires-builders: style
behlendorf
pushed a commit
that referenced
this issue
Feb 3, 2017
We must not use d_add_ci if the dentry already has the real name. Otherwise, d_add_ci()->d_alloc_parallel() will find itself on the lookup hash and wait on itself causing deadlock. Tested-by: satmandu Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Chunwei Chen <david.chen@osnexus.com> Closes #5124 Closes #5141 Closes #5147 Closes #5148
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Since updating to 0.6.5.5 one of my ZFS filesystems has become inaccesible.
ls /mountpoint hangs indefinitely, without any kind of error message or dmesg.
Failure still happens on 0.7.0-rc1.
Downgrading to 0.6.5.4 allows access to the filesystem.
Issue is not pool related, zpool and zfs commands work perfectly.
Sending the filesystem to another pool reproduces the fail.
Creating other filesystem on the same pool does not exhibit the fail.
It is the only filesystem on several pools I have with this failure.
zpool history only shows imports, scrubs and exports.
Scrub detects not a single failure.
The text was updated successfully, but these errors were encountered: