stack trace:
Core was generated by `/usr/bin/xrootd -l /var/log/xrootd/xrootd.log -c /etc/xrootd/xcache.cfg -k 7 -b'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f2e1ee438d7 in XrdFileCache::IOEntireFile::FSize (this=0x28f8900)
at /usr/src/debug/xrootd/xrootd/src/XrdFileCache/XrdFileCacheIOEntireFile.cc:75
75 {
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.212.el6.x86_64 gperftools-libs-2.0-11.el6.3.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-65.el6.x86_64 libcom_err-1.41.12-24.el6.x86_64 libgcc-4.4.7-23.el6.x86_64 libselinux-2.0.94-7.el6.x86_64 libstdc++-4.4.7-23.el6.x86_64 libunwind-1.1-3.el6.x86_64 libxml2-2.7.6-21.el6_8.1.x86_64 openssl-1.0.1e-57.el6.x86_64 zlib-1.2.3-29.el6.x86_64
(gdb) where
#0 0x00007f2e1ee438d7 in XrdFileCache::IOEntireFile::FSize (this=0x28f8900)
at /usr/src/debug/xrootd/xrootd/src/XrdFileCache/XrdFileCacheIOEntireFile.cc:75
#1 0x00007f2e1ee43a69 in XrdFileCache::IOEntireFile::Read (this=0x28f8900,
buff=0x3320000 "óM?\205\226???y??\205\"???ЬuT\\??+????qo??\022}C?????\235K??:\216?kp\214Y??\226\025|\226r\225=_Y?vH(r?Dzd?\212\017D\237?e\235?d\214?\207d\017?iz\026\177??4&|?~J{\224?\222<?\235??\"??)\031\024\212\036Si(?\022Ll?\025\036o?A#?;\023_???K\212\061?Y?_ڷ?D?D??g\220?,zX?y?#\024y٪\023;\233O87\024?{\a\206\"o~0kl???\226cX???\237\065\202?"..., off=34865152, size=262144)
at /usr/src/debug/xrootd/xrootd/src/XrdFileCache/XrdFileCacheIOEntireFile.cc:174
#2 0x00007f2e1ee4346d in XrdOucCacheIO2::Read (this=<value optimized out>, iocb=...,
buff=<value optimized out>, offs=<value optimized out>, rlen=<value optimized out>)
at /usr/src/debug/xrootd/xrootd/src/XrdOuc/XrdOucCache2.hh:106
#3 0x00007f2e1fff57b8 in XrdPssFile::Read (this=0x2a7a560, aiop=0x28eeb00)
at /usr/src/debug/xrootd/xrootd/src/XrdPss/XrdPssAio.cc:83
#4 0x00007f2e229bff51 in XrdOfsFile::read (this=0x2992400, aiop=0x28eeb00)
at /usr/src/debug/xrootd/xrootd/src/XrdOfs/XrdOfs.cc:976
#5 0x00007f2e2299e049 in XrdXrootdAioReq::Read (this=0x28ead28)
at /usr/src/debug/xrootd/xrootd/src/XrdXrootd/XrdXrootdAio.cc:400
#6 0x00007f2e2299e290 in XrdXrootdAioReq::endRead (this=0x28ead28)
at /usr/src/debug/xrootd/xrootd/src/XrdXrootd/XrdXrootdAio.cc:558
#7 0x00007f2e2273997b in XrdScheduler::Run (this=0x610378)
at /usr/src/debug/xrootd/xrootd/src/Xrd/XrdScheduler.cc:357
#8 0x00007f2e22739ac9 in XrdStartWorking (carg=<value optimized out>)
at /usr/src/debug/xrootd/xrootd/src/Xrd/XrdScheduler.cc:87
#9 0x00007f2e226f753f in XrdSysThread_Xeq (myargs=0x2659320)
at /usr/src/debug/xrootd/xrootd/src/XrdSys/XrdSysPthread.cc:86
#10 0x00007f2e222b2aa1 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f2e21657bdd in clone () from /lib64/libc.so.6
(gdb)
--
Wei Yang | [log in to unmask] | 650-926-3338 (O)
On 9/12/18, 2:38 PM, "[log in to unmask] on behalf of Yang, Wei" <[log in to unmask] on behalf of [log in to unmask]> wrote:
ATLAS reported a specific scenario that can crash Xcache. Assume that I have a file that is accessible from two xrootd doors:
root://host1//path/file
root://host2//path/file
If I access this file via Xcache simultaneously
root://xcache//root://host1//path/file
root://xcache//root://host2//path/file
Xcache will instantly crash. I guess it is because Xcache view these as two different files, but then maps them to the same cache entry.
--
Wei Yang | [log in to unmask] | 650-926-3338 (O)
########################################################################
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
