READY NAS 3312 Filled with Snapshots

[valeroso]

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 tried scrubbing and defrag without any luck.

Any help will be appreciated.

[StephenB]

• What firmware are you running?
• Do you have ssh enabled?

Enable "quota" via the volume settings wheel if it isn't enabled already.  Is the NAS showing snapshots for any share on the share page?

[valeroso]

---

@StephenB wrote:

• What firmware are you running?
• Do you have ssh enabled?

Enable "quota" via the volume settings wheel if it isn't enabled already.  Is the NAS showing snapshots for any share on the share page?

---

Firmware: 6.10.1

Yes, SSH is enabled.

Quota is enabled. The NAS is not showing any snapshots for any of the shares.

Screenshot is attached.

[StephenB]

Have you ever run a balance?  If you haven't, then try doing that.

[valeroso]

I have run the balance without any luck as well.

[StephenB]

About how old is the data volume?  Do you recall what firmware was installed when you created it?

[valeroso]

The data is just over a year old. I can't remember what version of firmware but I believe it was a 6.x release.

[StephenB]

---

@valeroso wrote:
The data is just over a year old. I can't remember what version of firmware but I believe it was a 6.x release.

---

They all are 6.x.  If the firmware was very old, there might have been a snapshot conversion step that failed.  However, if the NAS is ~1 year old, then that isn't the issue.

[valeroso]

Thank you for your help so far.

Any ideas what else I can try? 

[StephenB]

Check to see if btrfs sees the snapshots via ssh.

# btrfs subvolume list -s /data

Substitute your own volume name if you are using flexraid.

Perhaps post back with the list that you get.

[valeroso]

Apologies for the noob question.

Please how do I get to this mode # ? What I have is ~$ .

I have checked online without any luck

[StephenB]

From windows 10 you can just enter

ssh root@nas-ip-address

in the windows search bar - using the real NAS IP address of course.  If you have a mac, then you'd launch termimal and enter the same command from the prompt.

If you are using putty, then you'd enter root when you see the login prompt.

In all cases, you use the same password as the built-in admin account.

[valeroso]

Thank you!

That got me in.

Please see the output below:

ID 113110 gen 3509143 cgen 3509143 top level 260 otime 2019-06-28 10:05:13 path ._share/VEEAM_SHARE/.snapshot/b_1561709113_7399

[StephenB]

---

@valeroso wrote:

ID 113110 gen 3509143 cgen 3509143 top level 260 otime 2019-06-28 10:05:13 path ._share/VEEAM_SHARE/.snapshot/b_1561709113_7399

---

You can try 

# btrfs subvolume delete -c /data/._share/VREEM_SHARE/.snapshot/b_1561709113_7399

It's not a command I run very often - hopefully the syntax is exactly right.

The -c option tells btrfs to wait for the deletion to complete before returning.

[valeroso]

Seems the syntax was correct. However, I get the error below:

ERROR: Could not destroy subvolume/snapshot: Read-only file system

The storage is actually read-only now, possible due to the lack of space.

[StephenB]

---

@valeroso wrote:

The storage is actually read-only now, possible due to the lack of space.

---

Does 

# mount --bind -o rw /data /mnt

give you a read/write file system on /mnt?  (not sure it will, it's not something I've needed to do).

If it does, you could try the deletion using /mnt in the path instead of /data.

When done, you'd do

# umount /mnt

(note it's not unmount).

[valeroso]

/mnt doesn't give read write file system.

I get the same read-only error with /mnt.

[StephenB]

You could try remounting /data

# umount /data
# btrfs device scan
# btrfs fi show
# mount /dev/md127 /data

[valeroso]

I have done that. 

Now the command below returns no output

btrfs subvolume list -s /data

Checking the volume summary shows that there are no snapshots anymore but the drive is completely filled which is not possible.

The screenshot is attached.

[StephenB]

Are you seeing any files in /data???

You might need to reboot.

[valeroso]

I have restarted and can now see files under /data.

I am back to this point as:

Delete subvolume (commit): '/data/._share/VEEAM_SHARE/.snapshot/b_1561709113_7399'
ERROR: Could not destroy subvolume/snapshot: Read-only file system

[StephenB]

---

@valeroso wrote:

I have restarted and can now see files under /data.

I am back to this point as:

Delete subvolume (commit): '/data/._share/VEEAM_SHARE/.snapshot/b_1561709113_7399'
ERROR: Could not destroy subvolume/snapshot: Read-only file system

---

Well, this will continue until you can mount the volume as read-write.

Can you post /proc/mdstat?

[valeroso]

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]

A side note, I had this issue before. I updated the firmware and somehow that cleared the "snapshots"

I checked if there was a newer firmware I could update to but it appears I am already running the most recent firmware.

[StephenB]

---

@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