URL:
<http://savannah.cern.ch/support/?121133>
Summary: Having problems with oss.space on some "strange"
disks
Project: XROOTD
Submitted by: krasznaa
Submitted on: 2011-05-24 16:38
Category: None
Priority: 5 - Normal
Severity: 4 - Important
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: GNU/Linux
_______________________________________________________
Details:
Hi,
I'm trying to figure out the following: I'm setting up an XRootD server in a
standalone mode on a server. I have a number of different partitions mounted
under directories such as
/export/data1
/export/data2
...
/export/data6
The first two I've set up before the other 4, and those are on different
physical disks than the others. (I can describe the exact disk layout if
necessary, it's not completely trivial.)
I add these disks to the xrootd server's cache using lines such as
oss.space public /export/data1 xa
oss.space public /export/data2 xa
...
oss.space public /export/data6 xa
in my configuration. This seemed to work reasonably well, the initialization
log messages of xrootd tell me that it finds all the directories.
But I noticed this morning, that since I added the data3-data6 disks, files
copied to the server are not put into the cache directories correctly. I
export the directory "/atlas" with the simple configuration option
all.export /atlas
When I try to copy new files to this disk, I get the following messages in
the logfile on the server:
110524 12:16:59 19936 oss_FAttr: Unable to set attr XrdFrm.Pfn from
/export/data3/public/00/FBD9DB4D000000000E6%; operation not supported
As a result the file gets created in the /atlas directory physically instead
of being created under /export/data3/, and being linked to /atlas with a soft
link. The system works well if I only define the first two disks for the
cache. But I can't figure out what's different for these new partitions.
ls -l /export/ gives:
drwxr-xr-x 4 xrootd xrootd 4096 May 22 13:26 data1
drwxr-xr-x 4 xrootd xrootd 4096 May 18 19:04 data2
drwxr-xr-x 4 xrootd xrootd 4096 May 24 11:54 data3
drwxr-xr-x 4 xrootd xrootd 4096 May 24 11:54 data4
drwxr-xr-x 4 xrootd xrootd 4096 May 24 11:54 data5
drwxr-xr-x 4 xrootd xrootd 4096 May 24 11:54 data6
mount gives:
/dev/mapper/exportvg-e0data on /export/data1 type ext3 (rw)
/dev/mapper/exportvg-e1data on /export/data2 type ext3 (rw)
/dev/mapper/exportvg-e2data on /export/data3 type ext3 (rw)
/dev/mapper/exportvg-e3data on /export/data4 type ext3 (rw)
/dev/mapper/exportvg-e4data on /export/data5 type ext3 (rw)
/dev/mapper/exportvg-e5data on /export/data6 type ext3 (rw)
df -h gives:
/dev/mapper/exportvg-e0data
8.8T 53G 8.3T 1% /export/data1
/dev/mapper/exportvg-e1data
8.4T 172M 8.0T 1% /export/data2
/dev/mapper/exportvg-e2data
9.9T 165M 9.9T 1% /export/data3
/dev/mapper/exportvg-e3data
9.9T 165M 9.9T 1% /export/data4
/dev/mapper/exportvg-e4data
9.9T 165M 9.9T 1% /export/data5
/dev/mapper/exportvg-e5data
9.9T 165M 9.9T 1% /export/data6
(These are pretty large disks...)
But something is still different for these additional disks. Do you have any
idea what I managed to set up differently for them? It would be very
important that I figure this out.
Cheers,
Attila
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/support/?121133>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
