 |
 |
> On 15 Jun 2017, at 18:53, Yvan Calas <[log in to unmask]> wrote: > > I would like to understand how to correctly set up the parameter cms.space in XRootD. We currently observe error messages like this one on our servers: > > 170615 18:42:06 285690 XrootdXeq: alisgm76.15597:26@[::xxx.xxx.xx.x] pub IPv4 login as alisgm76 > 170615 18:42:06 285690 ofs_open: alisgm76.15597:26@[::xxx.xxx.xx.x] Unable to create /03/01818/8cb7a7f4-51e9-11e7-a169-ef6caac907fd; no space left on device > 170615 18:42:06 285690 XrootdXeq: alisgm76.15597:26@[::xxx.xxx.xx.x] disc 0:00:00 > > In order to solve this issue, I reduced the recalc parameter to 1 minutes and try different thresholds for the "min" and "hwm" parameters as described in [1]. Actually, we have: > > cms.space linger 0 recalc 1 min 100g 150g > > and the xrootd partition is as follow: > > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/datavg-data > 110T 110T 109G 100% /xrootd > > I tried to change the value of the hwm parameter (below and above 100g) but without success, the error messages remain. > > Could you please tell me if there is something wrong with my setting? I would like to add that some of our servers have a lot of free (available) space, so they should be chosen by the redirector IMHO. Do you think this is a bug (we are currently running XRootD v4.2.3-3). ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1