October 30, 20169 yr Hello, When I'm trying to copy files between folder shares that points only to one disk share and throught windows network then I get a call trace with this information: Oct 30 18:55:09 unHP kernel: Call Trace: Oct 30 18:55:09 unHP kernel: [<ffffffff812465cf>] xfs_alloc_fix_freelist+0x17f/0x2de Oct 30 18:55:09 unHP kernel: [<ffffffff81077469>] ? down_trylock+0x28/0x32 Oct 30 18:55:09 unHP kernel: [<ffffffff812738f8>] ? xfs_buf_trylock+0xd/0x17 Oct 30 18:55:09 unHP kernel: [<ffffffff81246829>] xfs_alloc_vextent+0xfb/0x3a3 Oct 30 18:55:09 unHP kernel: [<ffffffff81267313>] xfs_ialloc_ag_alloc+0x16e/0x649 Oct 30 18:55:09 unHP kernel: [<ffffffff81268a0d>] xfs_dialloc+0x12a/0x1f3 Oct 30 18:55:09 unHP kernel: [<ffffffff8106f1f5>] ? enqueue_entity+0x628/0x74c Oct 30 18:55:09 unHP kernel: [<ffffffff81280906>] xfs_ialloc+0x5d/0x472 Oct 30 18:55:09 unHP kernel: [<ffffffff8128a294>] ? kmem_zone_alloc+0x74/0xd0 Oct 30 18:55:09 unHP kernel: [<ffffffff81280d73>] xfs_dir_ialloc+0x58/0x197 Oct 30 18:55:09 unHP kernel: [<ffffffff8128115f>] xfs_create+0x26d/0x485 Oct 30 18:55:09 unHP kernel: [<ffffffff8127e53b>] xfs_generic_create+0xb6/0x23d Oct 30 18:55:09 unHP kernel: [<ffffffff81148a48>] ? get_acl+0x12/0x4f Oct 30 18:55:09 unHP kernel: [<ffffffff8127e6e7>] xfs_vn_mknod+0xf/0x11 Oct 30 18:55:09 unHP kernel: [<ffffffff8127e70a>] xfs_vn_create+0xe/0x10 Oct 30 18:55:09 unHP kernel: [<ffffffff8111230e>] vfs_create+0x68/0xa4 Oct 30 18:55:09 unHP kernel: [<ffffffff81114f18>] path_openat+0x60b/0xc45 Oct 30 18:55:09 unHP kernel: [<ffffffff81111bb7>] ? terminate_walk+0x21/0x82 Oct 30 18:55:09 unHP kernel: [<ffffffff81116484>] do_filp_open+0x48/0x9e Oct 30 18:55:09 unHP kernel: [<ffffffff811226d6>] ? mntput_no_expire+0x27/0x176 Oct 30 18:55:09 unHP kernel: [<ffffffff811208cd>] ? __alloc_fd+0x150/0x160 Oct 30 18:55:09 unHP kernel: [<ffffffff81109cf3>] do_sys_open+0x148/0x1d8 Oct 30 18:55:09 unHP kernel: [<ffffffff81109cf3>] ? do_sys_open+0x148/0x1d8 Oct 30 18:55:09 unHP kernel: [<ffffffff8111679f>] ? SyS_mkdirat+0x3a/0xac Oct 30 18:55:09 unHP kernel: [<ffffffff81109d9c>] SyS_open+0x19/0x1b Oct 30 18:55:09 unHP kernel: [<ffffffff816213ae>] entry_SYSCALL_64_fastpath+0x12/0x6d Oct 30 18:55:09 unHP kernel: Code: 01 8b 50 78 89 d6 83 ce 0a 80 e2 80 89 70 78 75 12 55 89 ca 44 89 ce 48 89 c7 48 89 e5 e8 c8 94 ff ff 5d c3 55 48 89 e5 41 54 53 <48> 8b 9e f8 00 00 00 f6 43 78 04 75 67 49 89 fc 48 89 f7 e8 fd Oct 30 18:55:09 unHP kernel: RIP [<ffffffff81295893>] xfs_trans_binval+0x7/0x80 Oct 30 18:55:09 unHP kernel: RSP <ffff8800d4e8f830> Oct 30 18:55:09 unHP kernel: CR2: 00000000000000f8 Oct 30 18:55:09 unHP kernel: ---[ end trace ff82ac5bfbd73f25 ]--- If you see the SMART properties for that disk then you will notice that disk has no errors reported. so I don't know what happened. Maybe the file system for that disk is corrupt? Thanks.
October 30, 20169 yr Read this thread: http://lime-technology.com/forum/index.php?topic=39073.msg363786#msg363786 Does your situation fall under the discussed scenario?
October 30, 20169 yr Community Expert That does look like filesystem corruption, check filesystem on that disk, but you do need to be careful with the user share copy bug, look at the thread linked above.
October 30, 20169 yr Author Hello, In my situation I took an external drive connected to windows then I tried to copy many files from this drive to a user share NOT a disk share, sorry. So this user share points to a only one disk on unraid.
November 1, 20169 yr Author Thanks johnnie and matt. It seems the xfs file system was corrupted and log too so first I use xfs_repair -L and then xfs_repair then the file system was repaired and no data loss.
Archived
This topic is now archived and is closed to further replies.