[
https://issues.apache.org/jira/browse/TS-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan van Doorn reopened TS-1319:
-------------------------------
The previous fix worked, but upon a restart the cache would be cleared like,
showing in the log:
[Jul 10 23:28:29.566] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdb 172032:109789184'
[Jul 10 23:28:29.621] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdc 172032:109789184'
[Jul 10 23:28:29.676] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdd 172032:109789184'
[Jul 10 23:28:29.730] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sde 172032:109789184'
[Jul 10 23:28:29.785] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdf 172032:109789184'
[Jul 10 23:28:29.837] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdg 172032:109789184'
[Jul 10 23:28:29.890] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdh 172032:109789184'
[Jul 10 23:28:29.943] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdi 172032:109789184'
[Jul 10 23:28:29.999] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdj 172032:109789184'
[Jul 10 23:28:30.053] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdk 172032:109789184'
[Jul 10 23:28:30.106] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdl 172032:109789184'
[Jul 10 23:28:30.160] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdm 172032:109789184'
[Jul 10 23:28:30.215] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdn 172032:109789184'
[Jul 10 23:28:30.268] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdo 172032:109789184'
[Jul 10 23:28:30.324] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdp 172032:109789184'
[Jul 10 23:28:30.379] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdq 172032:109789184'
[Jul 10 23:28:30.433] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdr 172032:109789184'
[Jul 10 23:28:30.493] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sds 172032:109789184'
[Jul 10 23:28:30.547] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdt 172032:109789184'
[Jul 10 23:28:30.601] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdu 172032:109789184'
[Jul 10 23:28:30.654] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdv 172032:109789184'
[Jul 10 23:28:30.707] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdw 172032:109789184'
[Jul 10 23:28:30.761] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdx 172032:109789184'
[Jul 10 23:28:30.814] Server {0x7fe09b5d17e0} NOTE: clearing cache directory
'/dev/sdy 172032:109789184'
[Jul 10 23:28:30.926] Server {0x7fe0977c9700} DEBUG: (cache_hosting) Host
Record: 0x7fdfd0000918, Volume: 1, size: 21585431887872
This patch will take care of that too, I think (doing testing now, will take a
while to fill this cache, not sure if it'll behave different with a full cache):
diff -r org/trafficserver-3.2.0/iocore/cache/Cache.cc
trafficserver-3.2.0/iocore/cache/Cache.cc
2236c2236
< int size_in_blocks = config_vol->size << (20 - STORE_BLOCK_SHIFT);
---
> off_t size_in_blocks = config_vol->size << (20 - STORE_BLOCK_SHIFT);
2352c2352
< Warning("the size of volume %d (%d) is less than the minimum required
volume size %d",
---
> Warning("the size of volume %d (%jd) is less than the minimum
> required volume size %d",
2356c2356
< Debug("cache_hosting", "Volume: %d Size: %d", config_vol->number,
config_vol->size);
---
> Debug("cache_hosting", "Volume: %d Size: %jd", config_vol->number,
> config_vol->size);
diff -r org/trafficserver-3.2.0/iocore/cache/CacheHosting.cc
trafficserver-3.2.0/iocore/cache/CacheHosting.cc
462c462
< Debug("cache_hosting", "Host Record: %p, Volume: %d, size: %u", this,
cachep->vol_number, cachep->size);
---
> Debug("cache_hosting", "Host Record: %p, Volume: %d, size: %jd", this,
> cachep->vol_number, cachep->size);
diff -r org/trafficserver-3.2.0/iocore/cache/P_CacheHosting.h
trafficserver-3.2.0/iocore/cache/P_CacheHosting.h
165c165
< int size;
---
> off_t size;
diff -r org/trafficserver-3.2.0/iocore/cache/P_CacheVol.h
trafficserver-3.2.0/iocore/cache/P_CacheVol.h
282c282
< int size;
---
> off_t size;
> Large cache (> 16TB) not working?
> ---------------------------------
>
> Key: TS-1319
> URL: https://issues.apache.org/jira/browse/TS-1319
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Affects Versions: 3.2.0
> Environment: Centos 6.1
> Reporter: Jan van Doorn
> Assignee: James Peach
> Fix For: 3.3.0
>
>
> Is there a maximum disk cache size in ATS 3.20? I seem to be getting this
> WARNING/Error:
> --
> [TrafficServer] using root directory '/opt/trafficserver'
> [Jun 21 21:57:10.038] {0x7f4d67aa67e0} STATUS: opened
> /opt/trafficserver/var/log/trafficserver/diags.log
> [Jun 21 21:57:10.038] {0x7f4d67aa67e0} NOTE: updated diags config
> [Jun 21 21:57:10.042] Server {0x7f4d67aa67e0} NOTE: cache clustering disabled
> [Jun 21 21:57:10.083] Server {0x7f4d67aa67e0} NOTE: cache clustering disabled
> [Jun 21 21:57:10.182] Server {0x7f4d67aa67e0} NOTE: logging initialized[11],
> logging_mode = 3
> [Jun 21 21:57:10.183] Server {0x7f4d67aa67e0} NOTE: loading plugin
> '/opt/trafficserver/libexec/trafficserver/stats_over_http.so'
> [Jun 21 21:57:10.185] Server {0x7f4d67aa67e0} NOTE: traffic server running
> [Jun 21 21:57:10.189] Server {0x7f4d63799700} WARNING: not enough space to
> increase volume: [1] to size: [20585472]
> [Jun 21 21:57:10.189] Server {0x7f4d63799700} NOTE: edit the volume.config
> file and restart traffic_server
> [Jun 21 21:57:10.189] Server {0x7f4d63799700} NOTE: cache disabled
> --
> When I try to use more than a certain amount (16TB?) of cache, and the "cache
> disabled" message doesn't seem good.
> I have a system with 24 600GB drives that works well, but a system with 24
> 900GB drives will have the above error, unless I disable at least 5 drives in
> storage.config.
> I tried splitting the cache up in to 2 volumes, each 50% in volume.config,
> but I still get the same error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
