NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 316 out of memory during Balance
ReadyNAS 316 6.9.2 RAID 5
Had a 11TB Lun with 1.7TB free space / 2 recent snapshots using about 5.7TB
Seemed like the snapshots were taking up a lot of space so I ran a Balance operation to see ...
I just want to follow up with my solution in case this helps anyone in the future. My data was intact on the iSCSI target and I disabled snapshots. I was unable to delete the existing snapshots through the web interface so my available space was still less than 20%. I used btrfs commands to find and delete those snapshots, rebooted and I am happy to report I have recovered all the space formerly used by the snapshots. The NAS has been stable and running for several weeks now. I appreciate the advice I was provided here and I found my solution from reading some of the other community posts.
UTSW-TX wrote:
Will this be solved by disabling snapshots in general or is there something inherent to modifying a lot of data while connected via LUN/iSCSI?
It's general, but is usually more problematic with LUNs than with shares.
When you first take a snapshot, it takes no space - all the data blocks are held in common with the main share. As the main share changes, any updated blocks are written as new blocks (e.g., "copy on write"). The original block then is in the snapshot only - so it now starts using space. And the updated file (or LUN) becomes fragmented.
So if you have a lot of updates happening in the share, the snapshots take a lot of space, and the main share (or LUN) quickly becomes fragmented. Defragmenting the file (LUN) in the main share actually makes the snapshot space go up. The main file is re-written, so it ends up sharing no blocks in common with the snapshot.
A LUN is simply raw block storage for the NAS - so operations that rewrite metadata or otherwise reorganize the storage are detrimental when snapshots are on. For instance, when snapshots are enabled, defragmenting the file system in the LUN will create fragmentation in the LUN container itself, and every disk block that is modified increases the snapshot space usage. So you end up with poor performance combined with a big loss of free space in the RAID array.
There are other cases where snapshots shouldn't be enabled. A torrent download creates similar "churn", as do updates to SQL databases.
I just want to follow up with my solution in case this helps anyone in the future. My data was intact on the iSCSI target and I disabled snapshots. I was unable to delete the existing snapshots through the web interface so my available space was still less than 20%. I used btrfs commands to find and delete those snapshots, rebooted and I am happy to report I have recovered all the space formerly used by the snapshots. The NAS has been stable and running for several weeks now. I appreciate the advice I was provided here and I found my solution from reading some of the other community posts.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
