Not sure what the cdot equivalent would be, but you could check "aggr show_space" from the nodeshell.

On Dec 9, 2015 3:07 AM, "Mike Thompson" <mike.thompson@gmail.com> wrote:
Hey all,

I've got a cluster running cluster-mode 8.0.5 (don't laugh) that has an aggregate which is reporting much higher used size than I can account for based on the volumes contained on it.

according to 'aggr show' and 'df -A' the aggregate has around 17T of space consumed.

bc-gx-4b::> aggr show -aggregate gx4b_1 -fields size, usedsize, availsize
aggregate size    usedsize availsize
--------- ------- -------- ---------
gx4b_1    18.40TB 17.08TB  1.32TB


though per my database, a tally of all the volumes contained on this aggregate, the total amount of space consumed by the volumes is only about 12.5T of space, so a significant amount is being soaked up by something.

I get the same numbers from the command line as well:

ssh admin@bc-gx-4b "set -units MB; vol show -aggregate gx4b_1 -fields used" | egrep "^bc" | awk '{print $3}' | sed 's/[^0-9]*//g' | paste -sd+ | bc
12528994


so the sum of the volumes is about 12.5T, but the aggregate thinks there is 17T used.

it's been in this state for some time.  There haven't been any volumes recently moved off or deleted, so there isn't any space being recovered in the background.

'vol show -state offline' and 'set diag; vol lost-found show' isn't reporting anything.

Any ideas on how I might figure out what is sucking up the un-reported space?


_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters