Hi Kashif,
I have seen this once and only found it when we got a ticket about files
not reachable. Not sure what happened back then.
What I did was to set it back to normal state using dpm-modifyfs. For your
filesystem it would be:
dpm-modifyfs --server t2se36.physics.ox.ac.uk --fs /dpm/pool3 --st 0
(helped for me, not sure if it's in general a good way to do so...)
Before changing anything, what I would check first is to see if /dpm/pool3
is still mounted and with the correct permissions on t2se36 and if you can
get a list of files under /dpm/pool3 from your database.
Cheers,
Marcus
On Thu, 16 Mar 2017, Kashif Mohammad wrote:
> Hi
>
> I noticed that in our dpm setup, one partition of a pool node has become 'disable' by itself
>
> dpm-qryconf --si
> ....
> t2se35.physics.ox.ac.uk /dpm/pool3 CAPACITY 6.48T FREE 133.54G ( 2.1%)
> t2se36.physics.ox.ac.uk /dpm/pool1 CAPACITY 6.50T FREE 130.55G ( 2.0%)
> t2se36.physics.ox.ac.uk /dpm/pool2 CAPACITY 6.50T FREE 130.59G ( 2.0%)
> t2se36.physics.ox.ac.uk /dpm/pool3 CAPACITY 0 FREE 175.99k ( 0.0%) DISABLED
> t2se37.physics.ox.ac.uk /dpm/pool1 CAPACITY 6.50T FREE 130.42G ( 2.0%)
> t2se37.physics.ox.ac.uk /dpm/pool2 CAPACITY 6.50T FREE 131.01G ( 2.0%)
>
> I can not see any error at server or at pool node. Has some one seen it earlier and what is best way to enable it ?
>
> Thanks
>
> Kashif
>
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
|