You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/05/04 03:07:13 UTC

[jira] [Updated] (TS-1612) RAW disk problem with CLFUS and compression enabled

     [ https://issues.apache.org/jira/browse/TS-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-1612:
------------------------------

    Labels: A  (was: )
    
> RAW disk problem with CLFUS and compression enabled
> ---------------------------------------------------
>
>                 Key: TS-1612
>                 URL: https://issues.apache.org/jira/browse/TS-1612
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cache
>            Reporter: Alex
>              Labels: A
>
> When you use RAW disk bigger than 2 x 2TB and you enable CLFUS algorithm along with compression (fastlz i tested with) you get segmentation faults:
> After enabling the debug mode I got seg fault in /usr/local/var/log/trafficserver/traffic.out
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /usr/local/bin/traffic_server - STACK TRACE:
> /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2b30fc503cb0]
> /usr/local/bin/traffic_server(_ZN23RamCacheCLFUSCompressor9mainEventEiP5Event+0xa4)[0x65d104]
> /usr/local/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0x86)[0x6a45c6]
> /usr/local/bin/traffic_server(_ZN7EThread7executeEv+0x31b)[0x6a4ebb]
> /usr/local/bin/traffic_server[0x6a33b2]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b30fc4fbe9a]
> /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b30fe3f5cbd]
> [E. Mgmt] log ==> [TrafficManager] using root directory '/usr/local'
> Tested with 8x2TB disks and 10x3TB disks. Without compression and using LRU algorithm everything works fine.
> ATS version (Apache Traffic Server - traffic_line - 3.3.1-dev - (build # 11315 on Dec  3 2012 at 15:51:14))

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira