NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
defcon84
Jan 23, 2020Guide
Readynas 3312 BTRFS error (device md127) in __btrfs_free_extent:6998: errno=-28 No space left
Hi, I have another issue with BTRFS. All the sudden, I couldn't write to the share. It gave the exception 'Permission denied'. I also could reset the shares permissions. So i tried to rese...
Sandshark
Jan 23, 2020Sensei
Yes, when there is an unrecoverable BTRFS error, one thing the OS tries is to make the volume read-only so you can make sure your backup is in order before something more happens (which likely would if writes were allowed). The only solution to this is normally a factory default and restoration of data from backup. It's a good idea to first check the SMART data for your drives just to be sure a hardware issue isn't the driving factor.
defcon84
Jan 24, 2020Guide
Thanks for the information.
Shouldn't a balance fix / prevent this?
smartctl doesn't show anything weird.
Anything else I can check?
For now, i'll copy the whole 80TB somewhere else and reset the NAS.
But this shouldn't be happening in a NAS, we buy them to use the RAID5, to prevent downtime.
- StephenBJan 24, 2020Guru - Experienced User
defcon84 wrote:
Anything else I can check?
This might resolve the error:
# btrfs-zero-log /dev/md127But there could be some missing or damaged files. The wanted 1820270 found 1820360 bit in the log means that there are 90 transactions in the journal that somehow didn't get written to the file system.
That could be due to disk errors, a system crash, or an unexpected power cut. So perhaps check the log zip for that stuff.
- defcon84Jan 24, 2020Guide
I have destroyed the Volume and recreated it, that seemed to get rid of the btrfs check errors (and the data offcourse).
Now it's rebuilding and than i'll get the data back. But i think it'll be fine for now.
- defcon84Jan 27, 2020Guide
It allready happened again:
...
parent transid verify failed on 8611392847872 wanted 8249 found 8252 parent transid verify failed on 8611392847872 wanted 8249 found 8252 ERROR: child eb corrupted: parent bytenr=8611405791232 item=335 parent level=1 child level=2 ERROR: failed to repair root items: Input/output errorif i try do the fix you proposed, it offcourse gives the mount exception:
root@SKNAS05:~# btrfs rescue zero-log /dev/md127 ERROR: /dev/md127 is currently mounted
What is the safest way to unmount fix and remount the volume?
Or do you think i'm better off with a factory reset (until now i only deleted and recreated the volume).
SMART gives me no errors, there was no system crash and no power loss.
- StephenBJan 27, 2020Guru - Experienced User
defcon84 wrote:
root@SKNAS05:~# btrfs rescue zero-log /dev/md127 ERROR: /dev/md127 is currently mounted
What is the safest way to unmount fix and remount the volume?
You could try unmounting it with umount, and then restarting - not sure if the umount will work, but it is safe to try.
The other option would be to boot into tech support mode.
But something is really wrong here - you shouldn't be seeing these problems over and over if you have healthy disks. I don't know what is going on, but I am wondering if you should pursue a warranty replacement.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!