NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RR3312 Copying Errors
Hello,
We have ReadyNAS 3312 (RR 3312 w/ 12 bay, Firmware: 6.10.3) that has been throwing volume alert message reading: "The volume data encountered an error and was made read-only. It is recommended to backup your data." when large amounts of data have been copied onto it. This has happened three times in the past few weeks and occured twice in one-day. Following the last alert, we left it in read-only mode until we could figure out the issue, which we have so far been unsuccessful at doing.
The following error message was in the kernel.log:
Jul 01 10:07:00 XXXXXXXXXX kernel: ------------[ cut here ]------------
Jul 01 10:07:00 XXXXXXXXXX kernel: WARNING: CPU: 1 PID: 4187 at fs/btrfs/extent-tree.c:7004 __btrfs_free_extent+0xaf4/0xb31()
Jul 01 10:07:00 XXXXXXXXXX kernel: BTRFS: Transaction aborted (error -28)
Jul 01 10:07:00 XXXXXXXXXX kernel: Modules linked in: vpd(PO)
Jul 01 10:07:00 XXXXXXXXXX kernel: CPU: 1 PID: 4187 Comm: btrfs-transacti Tainted: P O 4.4.190.x86_64.1 #1
Jul 01 10:07:00 XXXXXXXXXX kernel: Hardware name: NETGEAR ReadyNAS 3312/ReadyNAS RR3312, BIOS RR3312v113 01/25/2017
Jul 01 10:07:00 XXXXXXXXXX kernel: 0000000000000000 ffff8801baf7fa90 ffffffff8836360d ffff8801baf7fad8
Jul 01 10:07:00 XXXXXXXXXX kernel: 0000000000000009 ffff8801baf7fac8 ffffffff880dd1a8 ffffffff88282de0
Jul 01 10:07:00 XXXXXXXXXX kernel: 00000000ffffffe4 ffff880157a6ba10 ffff88026675a1e0 0000000000000000
Jul 01 10:07:00 XXXXXXXXXX kernel: Call Trace:
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff8836360d>] dump_stack+0x4d/0x63
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff880dd1a8>] warn_slowpath_common+0x8f/0xa8
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff88282de0>] ? __btrfs_free_extent+0xaf4/0xb31
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff88063f94>] warn_slowpath_fmt+0x47/0x49
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff882823d2>] ? __btrfs_free_extent+0xe6/0xb31
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff88282de0>] __btrfs_free_extent+0xaf4/0xb31
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff882e0154>] ? btrfs_merge_delayed_refs+0x60/0x43c
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff8828690c>] __btrfs_run_delayed_refs+0xa78/0xcbf
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff882886da>] btrfs_run_delayed_refs+0x66/0x24f
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff882892e7>] btrfs_write_dirty_block_groups+0x124/0x316
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff882888a8>] ? btrfs_run_delayed_refs+0x234/0x24f
Jul 01 10:07:00 XXXXXXXXXX kernel: [<ffffffff8829906d>] commit_cowonly_roots+0x208/0x2ac
The other two times it has gone down the kernal reads the same. It seems to indicate there is no space left, but in actuality there is ~60 TB free. We haven't been able to find the right solution from the forums so far. Would anyone know how to handle this?
10 Replies
Replies have been turned off for this discussion
It looks more like a corrupted file system to me. Is this happening on all shares, or just one in particular?
Thanks for the reply! Both shares are on the same volume, so its happening on both from our knowledge.
When the OS puts the volume in read-only mode, it is trying to protect the volume from further damage. Because it's read-only, the available space will show as zero, though if it really did fill up, that could be the root cause of the issue.
DO NOT reboot the NAS. It may come back up with a dead volume.
DO NOT attempt to make the volume read/write. It likely won't work, and you'll just be un-doing the protection and risking further damage to the voluime, including possible total loss.
DO do what it told you to do -- backup your files now. And backup your NAS configuration if it'll be painful to re-create. Hopefully, you have most of the files already backed up. Because some files may also now be corrupt, don't destroy your old one if at all possible.
There is something critically wrong with the volume that only destroying it and re-building it is likely going to solve. Netgear paid support may be able to do something, but it's doubtful. But you'll want that backup even before they try. If there is only one volume, a factory default is the best solution. But before you do that, you should also check to see if any of the drives has a problem that's the root cause of the issue you are encountering, and replace any that need it.
- We don't anticipate that the drive filled up, the data being moved over was on the order of GB when it has happened. So far, none of the drives have indicated any errors.How do we determine the root cause of the volume error? We prefer not to proceed with the rebuild until we know the root cause, and can ensure it won't happen again in the future. We do have backups of all the data, but there is so much data involved it takes a month to restore from the backups and validate the accuracy of the restoration. This ReadyNAS is less than a year old, so hopefully we don't have to completely rebuild ever year.Thank you for the response! I greatly appreciate it.
Logs in the downloaded .zip file are a good place to look to see if there is a hard drive that's giving you problems. Unfortunately, even new drives can fail.
I'm assuming that in a use case like yours, you have an UPS that is monitored by the NAS,. so a power interruption during a write operation isn't a possibility.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
