NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
READY NAS 3312 Filled with Snapshots
Hello, I have a ReadyNAS 3312 that shows snapshots are occupying almost half of the total space available. The confusing part is that I don't have snapshot enable on any of the shares. I have...
Here is the output
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid6 sda3[0] sdd3[7] sde3[6] sdb3[4] sdg3[3] sdf3[2] sdc3[1]
29278353920 blocks super 1.2 level 6, 64k chunk, algorithm 2 [7/7] [UUUUUUU]
md1 : active raid10 sda2[0] sdg2[6] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
1827840 blocks super 1.2 512K chunks 2 near-copies [7/7] [UUUUUUU]
md0 : active raid1 sda1[0] sdd1[7] sde1[6] sdb1[4] sdg1[3] sdf1[2] sdc1[1]
4190208 blocks super 1.2 [7/7] [UUUUUUU]
valeroso wrote:
Here is the output
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid6 sda3[0] sdd3[7] sde3[6] sdb3[4] sdg3[3] sdf3[2] sdc3[1]
29278353920 blocks super 1.2 level 6, 64k chunk, algorithm 2 [7/7] [UUUUUUU]md1 : active raid10 sda2[0] sdg2[6] sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1]
1827840 blocks super 1.2 512K chunks 2 near-copies [7/7] [UUUUUUU]md0 : active raid1 sda1[0] sdd1[7] sde1[6] sdb1[4] sdg1[3] sdf1[2] sdc1[1]
4190208 blocks super 1.2 [7/7] [UUUUUUU]
Ok. So the data volume only has one RAID group.
Maybe try
# mount -o rw /dev/md127 /mnt
Then see if /mnt is read/write
The mount is not successful
mount: wrong fs type, bad option, bad superblock on /dev/md127,
missing codepage or helper program, or other errorIn some cases useful info is found in syslog - try
dmesg | tail or so.Checking dmesg | tail gives below output
BTRFS error (device md127): Remounting read-write after error is not allowed
valeroso wrote:BTRFS error (device md127): Remounting read-write after error is not allowed
Ok. That command worked on one of my ReadyNAS, although /data was already mounted read/write.
Part of the puzzle here is figuring out why /data was mounted read-only when you booted - e.g. what that error was. Have you tried looking in the log zip? There might be some clues in there.
Another path is to open a support ticket, and have Netgear take it from here.
Looks like a support ticket with Netgear might be the way to go.
One final question though, is there any possibility that the RAID type(6) has any role to play on this?
I had a volume that went read-only because of an error. It took a couple minutes from boot before it went from read-write, so have you tried to jump in really fast and try the deletion? The log should say when it went read-only, so you can see if there is a window of opportunity there.
If you are using Putty, you can re-start the session and the command will still be in the buffer to cursor up and quickly re-execute.
Of course, if it's something else causing it to go read-only other than being full, you'll probably still end up needing to destroy the volume and restore from backup (I did). And doing that would also solve your snapshot problem (though take a long time).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
