sysconfig -r Volume vol0 (root)
RAID group 0
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) --------- ----- ------------ ---- -------------- -------------- parity 0a.5 0a 0 5 FC:A 8600/17612800 8683/17783112 data 0a.6 0a 0 6 FC:A 8600/17612800 8683/17783112 data 0a.1 0a 0 1 FC:A 8600/17612800 8683/17783112 data 0a.2 0a 0 2 FC:A 8600/17612800 8683/17783112 data 0a.3 0a 0 3 FC:A 8600/17612800 8683/17783112 data 0a.4 0a 0 4 FC:A 8600/17612800 8683/17783112
Spare disks
RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) --------- ----- ------------ ---- -------------- -------------- spare 0a.0 0a 0 0 FC:A 0 8683/17783112 Aspen> df Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 31627472 12681540 18945932 40% /vol/vol0/ /vol/vol0/.snapshot 7906864 366356 7540508 5% /vol/vol0/.snapsh ot
Above I have included the sysconfig -r and df commands from my filer which is a F720.
From the df I have 31627472KB +7906864KB= 39,534,336,000GB of available storage
From the sysconfig -r I have 5 data disks each with 8683 Physical MB so 5*8683MB= 43,415GB of available storage
or
From the sysconfig -r I have 5 data disk each with 8600 Used MB so 5*8600MB = 43GB of availabe storage
WHY IS MY AVAILABLE LOWER THAN IT SHOULD BE?
Thanks in advance,
Jason Middlebrooks Systems Engineer Datalink Corp. 888-933-9327 x2970 jmiddlebrooks@datalink.com jasonmiddlebrooks@yahoo.com
From the df I have 31627472KB +7906864KB= 39,534,336,000GB of available storage
No, you have 39,534,336 *KB* of available storage. Or 38,607.75 MB or 38.60775 GB.
From the sysconfig -r I have 5 data disks each with 8683 Physical MB so 5*8683MB= 43,415GB of available storage
No, because the physical storage isn't available for the filesystem. Disks are "right-sized" first.
or
From the sysconfig -r I have 5 data disk each with 8600 Used MB so
5*8600MB
= 43GB of availabe storage
Right. I'm pretty sure everywhere used in Netapp GB is 1000MB not 1024.
WHY IS MY AVAILABLE LOWER THAN IT SHOULD BE?
Because like most all filesystems (like UFS on UNIX), a certain portion of the space is "reserved" for filesystem overhead. WAFL reserves 10%. 43GB * .9 is 38.7 GB.
I'm not sure where your missing 92.25MB is. :)
Bruce
sirbruce@ix.netcom.com (Bruce Sterling Woodcock) writes: [...]
I'm not sure where your missing 92.25MB is. :)
It's (20.5 * 5 * 0.9) MB. :)
There's a 20.5 MB reserve, which is constant over all disc sizes I've seen (4GB, 9GB, 18GB; maybe someone can confirm it for 36GB). Presumably it's the fixed low-address area that was there even before right-sizing was invented.
So for jmiddlebrooks@datalink.com's system one calculates:
8600 MB (right-sized) - 20.5 MB = 8579.5 MB per disc inside the RAID4 regime;
x 5 data discs = 42897.5 MB;
x 0.9 maximum utilisation allowed = 38607.75 MB = 39534336 KB
which agrees exactly with the 31627472 + 7906864 KB shown by "df".
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.
There's a 20.5 MB reserve, which is constant over all disc sizes I've seen (4GB, 9GB, 18GB; maybe someone can confirm it for 36GB). Presumably it's the fixed low-address area that was there even before right-sizing was invented.
Yes, it's the space at the beginning of the disk used for boot blocks, disk labels, bootable kernel image, and core dump (not the core dump files, just the area to which main memory is dumped on a crash - "savecore" saves that to the file).
It's 5,248 4096-byte blocks.
-
Bruce Sterling Woodcock -
Chris Thompson -
Guy Harris -
jmiddlebrooksļ¼ datalink.com