-
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
PANIC at zfs_dir.c:784:zfs_link_create() #3222
Milestone
Comments
Code snippet for the ASSERT. error = zap_add(ZTOZSB(zp)->z_os, dzp->z_id, dl->dl_name,
8, 1, &value, tx);
ASSERT(error == 0); |
nedbass
added a commit
to nedbass/zfs
that referenced
this issue
Mar 25, 2015
When called to free a spill block from a dnode, dbuf_free_range() has a bug that results in all dbufs for the dnode getting freed. A variety of problems may result from this bug, but a common one was a zap lookup tripping an ASSERT because the zap buffers had been zeroed out. This could happen on a dataset with xattr=sa set when extended attributes are written and removed on a directory concurrently with I/O to files in that directory. Signed-off-by: Ned Bass <bass6@llnl.gov> Fixes openzfs#3195 Fixes openzfs#3222
nedbass
added a commit
to nedbass/zfs
that referenced
this issue
Mar 25, 2015
When called to free a spill block from a dnode, dbuf_free_range() has a bug that results in all dbufs for the dnode getting freed. A variety of problems may result from this bug, but a common one was a zap lookup tripping an ASSERT because the zap buffers had been zeroed out. This could happen on a dataset with xattr=sa set when extended attributes are written and removed on a directory concurrently with I/O to files in that directory. Signed-off-by: Ned Bass <bass6@llnl.gov> Fixes openzfs#3195 Fixes openzfs#3204 Fixes openzfs#3222
nedbass
added a commit
to nedbass/zfs
that referenced
this issue
Mar 25, 2015
When called to free a spill block from a dnode, dbuf_free_range() has a bug that results in all dbufs for the dnode getting freed. A variety of problems may result from this bug, but a common one was a zap lookup tripping an ASSERT because the zap buffers had been zeroed out. This could happen on a dataset with xattr=sa set when extended attributes are written and removed on a directory concurrently with I/O to files in that directory. Signed-off-by: Ned Bass <bass6@llnl.gov> Fixes openzfs#3195 Fixes openzfs#3204 Fixes openzfs#3222
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 4, 2015
When called to free a spill block from a dnode, dbuf_free_range() has a bug that results in all dbufs for the dnode getting freed. A variety of problems may result from this bug, but a common one was a zap lookup tripping an ASSERT because the zap buffers had been zeroed out. This could happen on a dataset with xattr=sa set when extended attributes are written and removed on a directory concurrently with I/O to files in that directory. Signed-off-by: Ned Bass <bass6@llnl.gov> Signed-off-by: Tim Chase <tim@chase2k.com> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Fixes openzfs#3195 Fixes openzfs#3204 Fixes openzfs#3222
DeHackEd
pushed a commit
to DeHackEd/zfs
that referenced
this issue
Apr 5, 2015
When called to free a spill block from a dnode, dbuf_free_range() has a bug that results in all dbufs for the dnode getting freed. A variety of problems may result from this bug, but a common one was a zap lookup tripping an ASSERT because the zap buffers had been zeroed out. This could happen on a dataset with xattr=sa set when extended attributes are written and removed on a directory concurrently with I/O to files in that directory. Signed-off-by: Ned Bass <bass6@llnl.gov> Signed-off-by: Tim Chase <tim@chase2k.com> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Fixes openzfs#3195 Fixes openzfs#3204 Fixes openzfs#3222
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Jun 9, 2015
When called to free a spill block from a dnode, dbuf_free_range() has a bug that results in all dbufs for the dnode getting freed. A variety of problems may result from this bug, but a common one was a zap lookup tripping an ASSERT because the zap buffers had been zeroed out. This could happen on a dataset with xattr=sa set when extended attributes are written and removed on a directory concurrently with I/O to files in that directory. Signed-off-by: Ned Bass <bass6@llnl.gov> Fixes openzfs#3195 Fixes openzfs#3222
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably related to #3195. The filesystem has
xattr=sa
set.Was using this stress test that writes random xattr to the directory while creating, removing, and writing data to files.
The text was updated successfully, but these errors were encountered: