On 2017-04-24 19:24, Zoltan Forray wrote:
> Collocation is also not a good choice.  Since this is the replication
> target and there are over 700-nodes, that would cause 700-filling volumes
> at all times.


No, if you collocate by group. So if for example you have 8 nodes in a
group, they would all use a single volume to fill.

But, of course - it all depends on the size of the nodes, size of the
volumes, retention period, total capacity, etc

And maybe you should consider converting your file pools to directory
container pools since you are using dedupe... But, you better upgrade
all servers to v7.1.7.x or v8.1 first...


Regards.

--
Sasa Drnjevic
www.srce.unizg.hr




>
> On Mon, Apr 24, 2017 at 9:41 AM, Sasa Drnjevic <Sasa.Drnjevic AT srce DOT hr>
> wrote:
>
>> On 24.4.2017. 15:29, Zoltan Forray wrote:
>>> On Mon, Apr 24, 2017 at 9:02 AM, Sasa Drnjevic <Sasa.Drnjevic AT srce DOT 
>>> hr>
>>> wrote:
>>>
>>>> -are those volumes R/W ?  if not, check ACTLOG
>>>>
>>>> -check MOUNTLimit for affected devclass(es)
>>>>
>>>> -check MAXSIze for affected stg pool(s)
>>>>
>>>
>>> Hi Sasa,
>>>
>>> Thank you for the hints.
>>>
>>> Yes, all are R/W.
>>>
>>> How does MOUNTLimit and MAXSize (set to NOLIMIT) effect the fillings?
>>
>>
>> In the case of disk which migrates to tape - if a disk volume is too
>> small to hold a big file, data store process will mount and directly use
>> tape instead of disk...
>>
>> Not, sure when only seq disk used...
>>
>> MOUNTLimit could make trouble if it's set too low, but it doesn't seem
>> to be that in your case...
>>
>> the question is why it is not reusing 0,5% filling volumes... Can you
>> try collocation on small group of nodes?
>>
>> Regards.
>>
>> --
>> Sasa Drnjevic
>> www.srce.unizg.hr
>>
>>
>>