Print

Print

@wyang007 Our xrootd system has the following characteristics:
There are a total of five XRootD Servers, some of which have a mix of SAN and NAS. The servers are running two XRootD disk server daemons, each managing files with different localroot directories.

It's hard to tell when the problem happened, but if my guess is correct, the problem probably started when the NAS mount directory sometimes hangs. If the NAS hangs, the xrootd server does not seem to be aware of it and will not reduce its capacity immediately, so if the write operation to that space is executed before the loss is reported, the xrootdfs_do_create () function will be able to fail.

If you can get the patch as an RPM format, I can apply it to that server. Of course, it can take quite a while, since the NAS mount must be hanged to reproduce it. However, if you give me a patch, I will continue the test.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1116?email_source=notifications\u0026email_token=AA7NRDQ3OR6ADYBRUVWAUCLRA574XA5CNFSM4KHM7UU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKSJ7WA#issuecomment-581214168", "url": "https://github.com/xrootd/xrootd/issues/1116?email_source=notifications\u0026email_token=AA7NRDQ3OR6ADYBRUVWAUCLRA574XA5CNFSM4KHM7UU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKSJ7WA#issuecomment-581214168", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1