NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN214 OS6.10.10 Snapshots
I found this post from 2021, but I am not seeing what I expect from snapshots. I have had this config for a long time, let's assume >2Y. I expected a monthly snapshot to be retained, as the d...
Yes quota is enabled. Snapshop pruning is set at 90%.
I can see see this in volume web I/F:
Snapshots taking 1.17GB - currently 8.79TB / 14.54TB used (~60%) where does this info show up in the logs?
I think there must have been an issue back when the auto-pruning was triggered. Since the volume now has plenty of free space, it must have been taken up by snapshots.
How would I be able to tell? The volume is 14.5TB, with 5.7TB free, with no significant deletions, and no addition of drives. This is the latest btrfs info:
# btrfs filesystem df /data
Data, single: total=8.79TiB, used=8.79TiB
System, RAID1: total=32.00MiB, used=992.00KiB
Metadata, RAID1: total=1.00GiB, used=19.34MiB
Metadata, DUP: total=1.00GiB, used=420.44MiB
GlobalReserve, single: total=68.22MiB, used=0.00B
# btrfs filesystem usage /data
Overall:
Device size: 14.54TiB
Device allocated: 8.80TiB
Device unallocated: 5.75TiB
Device missing: 0.00B
Used: 8.79TiB
Free (estimated): 5.75TiB (min: 2.88TiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 68.22MiB (used: 0.00B)
Thanks for looking.
How would I be able to tell? The volume is 14.5TB, with 5.7TB free, with no significant deletions, and no addition of drives
It would be hard to track down now, unless you have old log zips.
Note that snapshots take no space when first created - data blocks are mitrated to the snapshots only when the those blocks are no longer part of files in the main file system. Additional drives and new files do not increase snapshot size. Deletions, defrags, file updates (live databases, torrents, some backup software), and folder re-organization (since in many cases moves are really copy+delete) can all result in lots of snapshot space.
Your 14 September log snip shows at least two triggers for the pruning - 2025 June/July and 2026 April. Both show the system deleting old snapshots (more than one year back), so not the usual "thinning" (which removes snapshots at most 8 weeks old).
This appears to be the last of the triggered deletions in that snip:
[26/04/19 11:44:29 WEST] info:snapshot:LOGMSG_SMART_SNAPSHOT_DELETE_INFO Snapshot prune worker successfully deleted snapshot 2025_12_27__00_00_18 from share or LUN Shared.
The 90% threshold might possibly have triggered again after that date, so I guess you could double-check that.
I only have the logs from 3026-08-30 onwards (or much older), unfortunately.
Here is a refined list of snapshots and log entries:
2026-04-25 11:45:10 D120 2025-07-24 00:00:22 age: 275 0 no active snapshots 2026-05-03 00:00:52 C153 c_1777762851 1 oldest: 0 [153] 2026-05-11 00:00:15 C154 c_1778454014 2 oldest: 7 [153, 154] 2026-05-16 17:16:56 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-05-17 00:00:14 C155 c_1778972413 3 oldest: 13 [153, 154, 155] 2026-05-18 00:00:15 C156 c_1779058814 4 oldest: 14 [153, 154, 155, 156] 2026-05-31 01:19:44 D153 2026-05-03 00:00:52 age: 28 3 oldest: 20 [154, 155, 156] 2026-06-08 15:21:11 D154 2026-05-11 00:00:15 age: 28 2 oldest: 22 [155, 156] 2026-06-14 00:00:18 C157 c_1781391617 3 oldest: 28 [155, 156, 157] 2026-06-14 00:22:07 D155 2026-05-17 00:00:14 age: 28 2 oldest: 27 [156, 157] 2026-06-29 00:00:05 C158 c_1782687604 3 oldest: 41 [156, 157, 158] 2026-07-06 18:15:47 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-07-12 00:00:31 C159 c_1783810830 4 oldest: 55 [156, 157, 158, 159] 2026-07-12 00:18:25 D157 2026-06-14 00:00:18 age: 28 3 oldest: 55 [156, 158, 159] 2026-07-14 00:00:30 C160 c_1783983629 4 oldest: 57 [156, 158, 159, 160] 2026-07-25 17:25:02 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-08-09 01:28:57 D159 2026-07-12 00:00:31 age: 28 3 oldest: 83 [156, 158, 160] 2026-08-11 03:30:00 D160 2026-07-14 00:00:30 age: 28 2 oldest: 85 [156, 158] 2026-08-11 09:30:09 D158 2026-06-29 00:00:05 age: 43 1 oldest: 85 [156] 2026-08-11 10:30:19 D156 2026-05-18 00:00:15 age: 85 0 no active snapshots 2026-08-12 00:00:08 C161 c_1786489206 1 oldest: 0 [161] 2026-08-13 00:00:09 C162 c_1786575608 2 oldest: 1 [161, 162] 2026-08-16 00:00:10 C163 c_1786834809 3 oldest: 4 [161, 162, 163] 2026-08-17 00:00:14 C164 c_1786921212 4 oldest: 5 [161, 162, 163, 164] 2026-08-17 19:12:10 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-08-18 00:00:28 C165 c_1787007626 5 oldest: 6 [161, 162, 163, 164, 165] 2026-08-20 00:00:03 C166 c_1787180402 6 oldest: 7 [161, 162, 163, 164, 165, 166] 2026-08-21 00:00:07 C167 c_1787266805 7 oldest: 8 [161, 162, 163, 164, 165, 166, 167] 2026-08-21 12:08:04 notice:volume:LOGMSG_BALANCE_STARTED_VOLUME Balance started for volume data. 2026-08-21 12:08:06 notice:volume:LOGMSG_BALANCE_COMPLETED_VOLUME Balance complete for volume data. 2026-08-21 12:08:51 notice:volume:LOGMSG_DEFRAGSTART_VOLUME Defragmentation started for volume data. 2026-08-21 12:20:00 notice:volume:LOGMSG_DEFRAGEND_VOLUME Defragmentation complete for volume data. 2026-08-24 20:49:26 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-08-29 00:00:09 C168 c_1787958007 8 oldest: 17 [161, 162, 163, 164, 165, 166, 167, 168] 2026-08-30 00:00:12 C169 c_1788044411 9 oldest: 18 [161, 162, 163, 164, 165, 166, 167, 168, 169] 2026-08-31 00:00:14 C170 c_1788130813 10 oldest: 19 [161, 162, 163, 164, 165, 166, 167, 168, 169, 170] 2026-09-02 09:38:43 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-09-04 09:44:33 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-09-05 23:39:25 C171 Manual-snapshot-2026-09-05 11 oldest: 24 [161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171] 2026-09-06 00:00:01 C172 c_1788649200 12 oldest: 24 [161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172] 2026-09-07 20:02:45 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-09-08 07:47:19 notice:volume:LOGMSG_SCRUBSTARTED_VOLUME Scrub started for volume data. 2026-09-08 19:40:14 notice:volume:LOGMSG_SCRUBSTOP_VOLUME Scrub stopped for volume data. 2026-09-11 21:05:19 D162 2026-08-13 00:00:09 age: 29 11 oldest: 30 [161, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172] 2026-09-11 21:05:19 D161 2026-08-12 00:00:08 age: 30 10 oldest: 26 [163, 164, 165, 166, 167, 168, 169, 170, 171, 172] 2026-09-13 10:05:28 D163 2026-08-16 00:00:10 age: 28 9 oldest: 27 [164, 165, 166, 167, 168, 169, 170, 171, 172] 2026-09-14 14:05:45 D164 2026-08-17 00:00:14 age: 28 8 oldest: 27 [165, 166, 167, 168, 169, 170, 171, 172] 2026-09-15 09:06:10 D165 2026-08-18 00:00:28 age: 28 7 oldest: 26 [166, 167, 168, 169, 170, 171, 172] 2026-09-17 08:06:44 D166 2026-08-20 00:00:03 age: 28 6 oldest: 27 [167, 168, 169, 170, 171, 172] 2026-09-17 08:34:46 C173 2026-09-17_manual 7 oldest: 27 [167, 168, 169, 170, 171, 172, 173] 2026-09-19 18:00:09 D167 2026-08-21 00:00:07 age: 29 6 oldest: 21 [168, 169, 170, 171, 172, 173] 2026-09-19 18:00:23 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-09-20 11:58:37 info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. 2026-09-20 22:12:23 notice:volume:LOGMSG_BALANCE_STARTED_VOLUME Balance started for volume data. 2026-09-20 22:12:42 notice:volume:LOGMSG_BALANCE_COMPLETED_VOLUME Balance complete for volume data.This shows further automated deletions are ongoing.
This shows further automated deletions are ongoing.
Where exactly are you looking? I'm not seeing something formatted like your entries in my zip files.
It might be easier to sort out if this is now working properly by looking in snapper.log.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
