NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Paladax's avatar
Paladax
Aspirant
Feb 06, 2014

Readynas 3200 disk space issue

Hi there,

I have 2 of these units with both 12X 2tB disks in them. One unit it the primary unit that is where all my other site servers backup to. That then mirrors the data onto the 2nd offsite unit.

Now the issue I have is that the source server is showing that these backup folders are only taking up 6.7TB whereas the offsite one is showing that the backup folder is 17TB. And the offsite one is showing as full now. They have always been set to delete files on target that do not exist on source, but I don't get how this discrepancy could have occurred. I have tried going through it manually and I can't see any data there on the offsite backup that should not be there. Just some out of data stuff as the backup hasn't been going for a little while now due to this full issue.

I tried over Christmas going in and deleting the individual folders within the backup folder on the offsite backup, then just copying 1 days backup and synching that then across all to other days, then tried to let the backup take over again and synch, but it just filled up the remaining space (it was only about 80% full at that point).

Any ideas?

5 Replies

Replies have been turned off for this discussion
  • I have noticed something further on this issue and wondered if it was a Netgear "quirk" or if perhaps I have a problem with my data.

    When I look at the space size of a folder in my backups. My Monday- Friday folder size show me a different size to if I actually go inside the Mon-Fri folders and then do a directory size inside of there.

    For instance. If I am in a backup folder for a server and do a du * -sh it shows the following

    Mon = 436GB
    Tue = 73GB
    Wed = 71GB
    Thur = 80GB
    Fri = 436GB

    However, if I then go into the Wednesday folder and do the same du command it then shows me a total size of 436GB.

    Is this right??
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    What version of RAIDiator are you using?

    I assume you are using Rsync?
  • Paladax wrote:
    If I am in a backup folder for a server and do a du * -sh it shows the following

    Mon = 436GB
    Tue = 73GB
    Wed = 71GB
    Thur = 80GB
    Fri = 436GB

    However, if I then go into the Wednesday folder and do the same du command it then shows me a total size of 436GB.


    That's correct if your backups are created using hardlinks (e.g. using the rsync "--link-dest" option); du counts each file it sees only once, regardless of how many hardlinks to that file it also sees.

    To make du count every hardlink, try this from your outer directory:
    du -shl *
  • Hi Fastfwd,

    Thanks, that explained the why a little better. Only now it is a bit more confusing because if i do that command from the root folder of my backups it tells me my backups are 22TB.. however the NAS itself it only 18TB.

    If that is right though it would explain why the other 18TB was filling up when I tried to mirror the data onto it while the source one was still showing only 42% full.
  • Paladax wrote:
    Thanks, that explained the why a little better. Only now it is a bit more confusing because if i do that command from the root folder of my backups it tells me my backups are 22TB.. however the NAS itself it only 18TB.

    Right. For example, imagine a parent directory containing four empty child directories:

    NAS2:~/parent# du -h
    4.0K ./child0
    4.0K ./child3
    4.0K ./child1
    4.0K ./child2
    20K .


    Now we create a 100MB file in child0, and create hardlinks to that file in child1, child2, and child3:

    NAS2:~/parent# dd if=/dev/zero of=./child0/file count=204000
    204000+0 records in
    204000+0 records out
    104448000 bytes (104 MB) copied, 2.19748 s, 47.5 MB/s

    NAS2:~/parent# ln ./child0/file ./child1/link1
    NAS2:~/parent# ln ./child0/file ./child2/link2
    NAS2:~/parent# ln ./child0/file ./child3/link3


    To the "ls" program, each of the links looks like a 100MB file:

    NAS2:~/parent# l -Rh
    .:
    total 16K
    drwxr-xr-x 2 root root 4.0K Mar 6 13:06 child0
    drwxr-xr-x 2 root root 4.0K Mar 6 13:07 child1
    drwxr-xr-x 2 root root 4.0K Mar 6 13:07 child2
    drwxr-xr-x 2 root root 4.0K Mar 6 13:07 child3

    ./child0:
    total 100M
    -rw-r--r-- 4 root root 100M Mar 6 13:06 file

    ./child1:
    total 100M
    -rw-r--r-- 4 root root 100M Mar 6 13:06 link1

    ./child2:
    total 100M
    -rw-r--r-- 4 root root 100M Mar 6 13:06 link2

    ./child3:
    total 100M
    -rw-r--r-- 4 root root 100M Mar 6 13:06 link3


    But if we do a "du", we see the truth:
    NAS2:~/parent# du -h
    100M ./child0
    4.0K ./child3
    4.0K ./child1
    4.0K ./child2
    100M .


    Unless we use the "-l" option to force du to treat links as though they're files:
    NAS2:~/parent# du -hl
    100M ./child0
    100M ./child3
    100M ./child1
    100M ./child2
    399M .


    Paladax wrote:
    If that is right though it would explain why the other 18TB was filling up when I tried to mirror the data onto it while the source one was still showing only 42% full.

    Yes. The program performing the copy was treating links as though they were the linked-to files. If you had used it on my example, it would have created four 100MB files on the destination drive rather than one 100MB file and three links.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More