 |
 |
Ho Doug, Sorry to hear that. The answer is yes, you can have that capability. Simply specify the actual partitions you want to use via the oss.space directive and omit the faulty ones (i.e., do't use an asterisk). Omitted ones will automatically become read-only. So, xrootd does have most of the features you really want when you get into trouble :-) Andy -----Original Message----- From: Yang, Wei Sent: Thursday, March 26, 2015 3:56 PM To: Doug Benjamin Cc: Patrick McGuigan ; xrootd-l Subject: Re: xrootd system reporting no space left on device but there are sufficient inodes and disk space I don’t think we have such a flexibility in xrootd. Can a reboot clear the xfs issue? Wei Yang | [log in to unmask] | 650-926-3338(O) On Mar 26, 2015, at 2:59 PM, Doug Benjamin <[log in to unmask]> wrote: > Hi Wei, > > Thanks for the tip. It appears that it is a problem with one of the > disks /data/2. It is a xfs file system on top of lvm > and xfs_repair is not locating any problems. The xfs database is stating > that ifree=0. > > Not sure how I can fix the issue with this file system. > > Is there a way to have one of the two drives in the oss.space public > /data/* be readonly and the other r/w ? > > Thanks, > > Doug ######################################################################## 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 ######################################################################## 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