How big is each LUN in the storage pool (old & new)? I don't have
anything concrete to base this on other than I think I saw it work
this way when playing in the lab, but I think that XSAN will only add
the smallest size of an existing stripe group's LUNs.
(for example, if you have a stripe group with 5 LUNs of 1TB each, then
you add a sixth LUN of 1.5TB, you'll only get 1TB of the sixth LUN).
Best way to tell the size of the luns is probably to gather the number
of blocks using cvlabel -l .
-dalvenjah
On Feb 5, 2009, at 2:32 PM, Vilius Šumskas wrote:
Hi,
Today I had an opportunity first time in my life to expand an Xsan 2
volume
by adding a new LUN into current storage pool. All went well except
that
before the addition I had ~300gb free on my volume and I have added
2,73TB
LUN. But df -h shows only 2,4TB after the expansion. I'm wondering
where
another 600gb gone missing? Maybe these lines in the logs are
related?:
Feb 6 00:07:34 xserve3 fsm[621]: Xsan FSS 'EditSAN[0]': FSM Alloc:
Stripe
Group "Pool1" 161613356 free blocks in 8348149 fragments inserted.
Feb 6 00:07:34 xserve3 fsm[621]: Xsan FSS 'EditSAN[0]': FSM Alloc:
Stripe
Group "Pool1" 43967110 free blocks in 2700088 fragments ignored.
43967110 * 16KB ~ 600gb (???)
--
Best Regards,
Vilius Šumskas
LNK TV IT manager
mob.: +370 614 75713
http://www.lnk.lt
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
