NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Miraculix1
Aug 22, 2017Tutor
Resource busy
Hi,
I just updated my RN516 with FW 6.8.0. I use my NAS with OSX Sierra, connected with SMB, and I do have problems deleting files useing finder.
When I try to delete a file with OSX Finder I get the error "resource busy".
Useing the WebUI of RN516 I can delete the file.
I did not change system settings, I only updated to 6.8.0 and activated Mac OSX special in the smb settings of the NAS (disableing this switch does not help)
How can I solve my problem.
I did not find a solution for this problem, today I updated to 6.9.0 RC1.
Now the smb access works fine.
This behaviour is not mentioned in the update notice, but it solved my problem.
16 Replies
Replies have been turned off for this discussion
- evan2NETGEAR Expert
Which OSX Sierra version are you running?
I can't reproduce the issue on My MacOS Sierra 10.12.5, test NAS is RN422 6.8.0.
Could you please send logs?
How do I send all logs to ReadyNAS Community moderators?
https://kb.netgear.com/21543/How-do-I-send-all-logs-to-ReadyNAS-Community-moderatorsHi Evan,
thanks for the quick response.
Sierra 10.12.6 is installed.
The log is on its way
Miraculix
- evan2NETGEAR Expert
I checked there is btrfs warning on you NAS, I am not sure if it is root cause, but the problem need to fix.
Aug 20 13:29:42 Vierings-Daten kernel: BTRFS warning (device md127): qgroup 12508 reserved space underflow, have: 0, to free: 4096 Aug 20 13:29:42 Vierings-Daten kernel: ------------[ cut here ]------------ Aug 20 13:29:42 Vierings-Daten kernel: WARNING: CPU: 1 PID: 3348 at fs/btrfs/qgroup.c:2480 btrfs_qgroup_free_refroot+0x140/0x170() Aug 20 13:29:42 Vierings-Daten kernel: Modules linked in: sx8635(O) vpd(PO) Aug 20 13:29:42 Vierings-Daten kernel: CPU: 1 PID: 3348 Comm: btrfs-transacti Tainted: P W O 4.4.79.x86_64.1 #1 Aug 20 13:29:42 Vierings-Daten kernel: Hardware name: NETGEAR ReadyNAS 516/To be filled by O.E.M., BIOS 4.6.5 10/11/2013 Aug 20 13:29:42 Vierings-Daten kernel: 0000000000000000 ffff8800a8aabc58 ffffffff883d9498 0000000000000000 Aug 20 13:29:42 Vierings-Daten kernel: ffffffff88cfc618 ffff8800a8aabc90 ffffffff8806e41c ffff8800a8b03808 Aug 20 13:29:42 Vierings-Daten kernel: ffff8800a8b03780 0000000000001000 ffff880119efc000 0000000000000000 Aug 20 13:29:42 Vierings-Daten kernel: Call Trace: Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff883d9498>] dump_stack+0x4d/0x65 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff8806e41c>] warn_slowpath_common+0x7c/0xb0 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff8806e505>] warn_slowpath_null+0x15/0x20 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff8835e7c0>] btrfs_qgroup_free_refroot+0x140/0x170 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff882d9b21>] __btrfs_run_delayed_refs+0x2c1/0x10a0 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff88097513>] ? dequeue_task_fair+0x5b3/0x880 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff8809845e>] ? put_prev_entity+0x2e/0x700 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff880b761f>] ? lock_timer_base.isra.24+0x4f/0x70 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff882dd7dd>] btrfs_run_delayed_refs+0x7d/0x2e0 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff882f34e4>] btrfs_commit_transaction+0x24/0x60 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff882ee056>] transaction_kthread+0x216/0x230 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff882ede40>] ? btrfs_cleanup_transaction+0x4a0/0x4a0 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff88088296>] kthread+0xe6/0x100 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff880881b0>] ? kthread_create_on_node+0x170/0x170 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff88a58a1f>] ret_from_fork+0x3f/0x70 Aug 20 13:29:42 Vierings-Daten kernel: [<ffffffff880881b0>] ? kthread_create_on_node+0x170/0x170 Aug 20 13:29:42 Vierings-Daten kernel: ---[ end trace 54ab9bdf11da690b ]--- Aug 20 13:29:42 Vierings-Daten kernel: BTRFS warning (device md127): qgroup 12508 reserved space underflow, have: 0, to free: 4096
Could do you please enable sceure diagnotic? I need to ask our developter to remote access to fix it.
RAIDar Secure diagnostic
https://kb.netgear.com/27391/ReadyNAS-RAIDar-6-0
or enable secure diagnosticn in NAS admin GUI =>System=>Settings=>Support,the PM me 5 digital.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!