- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
NV+ v1 (4.1.16) How to increase Time Machine capacity?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all,
I am in need of assistance with increasing the available space for Time Machine backups...
I have an NV+ V1 that I just upgraded from 4.1.14 to 4.1.16. I am trying to create a *new* Time Machine backup, but the TM preferences pane is reporting only 109GB of 1.4TB are available (my new sparsebundle will be at least 1TB.) The TM configuration panel in FrontView is reporting a max capactity of 1342GB; however, the Volume Setting panel is reporting 1392GB of 2743GB in use.
So, how can I increase the available capactity for TM backups? I have four 1TB drive in an X-RAID configuration. The relevant shell outputs are below.
Thank you,
Ira
LupoNAS:/# repquota -as
*** Report for user quotas on device /dev/c/c
Block grace time: 30days; Inode grace time: 30days
Block limits File limits
User used soft hard grace used soft hard grace
----------------------------------------------------------------------
root -- 123M 0 0 62 0 0
admin -- 128 0 0 5 0 0
NAS_Backups -- 40 0 0 10 0 0
NAS_Media -- 1264M 0 0 16 0 0
sandy +- 1419M 1200M 1500M 29days 6943 0 0
iwolf -- 150G 157G 196G 11975 0 0
NAS_Users -- 4 0 0 1 0 0
ReadyNAS -- 1241G 1342G 1342G 318k 0 0
LupoNAS:/# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 555M 1.3G 29% /
tmpfs 16k 0 16k 0% /USB
/dev/c/c 2.7T 1.4T 1.3T 51% /c
LupoNAS:/# uname -a
Linux LupoNAS 2.6.17.14ReadyNAS #1 Wed Jun 20 20:08:20 PDT 2012 padre unknown
LupoNAS:/#
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, I figured it out with the use of setquota as referenced in a similar but older thread. The trick is that the max limit (for me) is 2000GB, not 2TB (2048GB.). The 2048GB value wouldn't stick (i.e. setquota passed, but repquota showed the old value.)
Now to understand why 2000GB is the max quota value in 4.1.16, while the NAS capacity is 2.7TB in a 4x1TB XRAID configuration...
Best,
Ira
LupoNAS:~# setquota -u ReadyNAS 2097152000 2097152000 0 0 /dev/c/c
LupoNAS:~# repquota -as
*** Report for user quotas on device /dev/c/c
Block grace time: 30days; Inode grace time: 30days
Block limits File limits
User used soft hard grace used soft hard grace
----------------------------------------------------------------------
root -- 123M 0 0 50 0 0
admin -- 128 0 0 5 0 0
NAS_Backups -- 40 0 0 10 0 0
NAS_Media -- 1264M 0 0 16 0 0
sandy +- 1419M 1200M 1500M 29days 6943 0 0
iwolf -- 150G 157G 196G 11975 0 0
NAS_Users -- 4 0 0 1 0 0
ReadyNAS -- 1193G 2000G 2000G 305k 0 0
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, I figured it out with the use of setquota as referenced in a similar but older thread. The trick is that the max limit (for me) is 2000GB, not 2TB (2048GB.). The 2048GB value wouldn't stick (i.e. setquota passed, but repquota showed the old value.)
Now to understand why 2000GB is the max quota value in 4.1.16, while the NAS capacity is 2.7TB in a 4x1TB XRAID configuration...
Best,
Ira
LupoNAS:~# setquota -u ReadyNAS 2097152000 2097152000 0 0 /dev/c/c
LupoNAS:~# repquota -as
*** Report for user quotas on device /dev/c/c
Block grace time: 30days; Inode grace time: 30days
Block limits File limits
User used soft hard grace used soft hard grace
----------------------------------------------------------------------
root -- 123M 0 0 50 0 0
admin -- 128 0 0 5 0 0
NAS_Backups -- 40 0 0 10 0 0
NAS_Media -- 1264M 0 0 16 0 0
sandy +- 1419M 1200M 1500M 29days 6943 0 0
iwolf -- 150G 157G 196G 11975 0 0
NAS_Users -- 4 0 0 1 0 0
ReadyNAS -- 1193G 2000G 2000G 305k 0 0