[OmniOS-discuss] zfs send/receive corruption?
Aaron Curry
asc1111 at gmail.com
Mon Oct 5 16:45:37 UTC 2015
We have a file server implementing CIFS to serve files to our users.
Periodic snapshots are replicated to a secondary system via zfs
send/receive. I recently moved services (shares, ip addresses, etc) to the
secondary system while we performed some maintenance on the primary server.
Shortly after everything was up and running on the secondary system, that
server panic'ed. Here's the stack trace:
panicstr = assertion failed: 0 == zfs_acl_node_read(dzp, B_TRUE, &paclp,
B_FALSE), file: ../../common/fs/zfs/zfs_acl.c, line: 1717
panicstack = fffffffffba8b1a8 () | zfs:zfs_acl_ids_create+4d2 () |
zfs:zfs_make_xattrdir+96 () | zfs:zfs_get_xattrdir+103 () |
zfs:zfs_lookup+1b6 () | genunix:fop_lookup+a2 () |
genunix:xattr_dir_realdir+b3 () | genunix:xattr_lookup_cb+65 () |
genunix:gfs_dir_lookup_dynamic+7c () | genunix:gfs_dir_lookup+18c () |
genunix:gfs_vop_lookup+35 () | genunix:fop_lookup+a2 () |
smbsrv:smb_vop_lookup+ea () | smbsrv:smb_vop_stream_lookup+e5 () |
smbsrv:smb_fsop_lookup_name+158 () | smbsrv:smb_open_subr+1b8 () |
smbsrv:smb_common_open+54 () | smbsrv:smb_com_nt_create_andx+ac () |
smbsrv:smb_dispatch_request+687 () | smbsrv:smb_session_worker+a0 () |
genunix:taskq_d_thread+b7 () | unix:thread_start+8 () |
Luckily, it wasn't hard to identify the steps to reproduce the problem.
Accessing a particular directory from a Mac OS X system causes this panic
every time, but only on the secondary (zfs send/receive target) system.
Accessing the same directory on the primary system does not cause a panic.
I have tested this on other systems and have been able to reproduce the
panic on the zfs send/receive target every time. Also, I have been able to
reproduce it with OmniOS versions 151010, 151012 and the latest 151014.
Replicating between two separate system and replicating to the local system
both exhibit the same behavior.
While I have been able to reliably pin the down a particular file or
file/directory combination that is causing the problem and can easily
reproduce the panic, I am at a loss of where to go from here. Are there any
known issues with zfs send/receive? Any help would be appreciated.
Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20151005/7fb6652c/attachment.html>
More information about the OmniOS-discuss
mailing list