Thanks James-
Looks like it detected the drive size properly, however the cache init is
still failing. I removed the /dev/ram* devices from storage.config just in case
they were causing a problem. I also added another 4GB virtual drive just to see
if more disk space was needed.
[Jun 9 23:29:06.391] Server {0x7ffe0ceba800} DEBUG: (cache_init)
Store::read_config - ns = new Span; ns->init("/dev/vdb",-1), forced volume=1
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init)
Store::read_config, fd = -1,
"/opt/trafficserver/etc/trafficserver/storage.config"
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init)
Store::read_config: "/dev/vdb"
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init)
Store::read_config - ns = new Span; ns->init("/dev/vdb",-1), forced volume=1
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init) initialized
span '/dev/vdb'
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init)
hw_sector_size=512, size=1073741824, blocks=131072, disk_id=0/64528,
file_pathname=1
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init)
Store::read_config: "/dev/vdc"
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init)
Store::read_config - ns = new Span; ns->init("/dev/vdc",-1), forced volume=1
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init) initialized
span '/dev/vdc'
[Jun 10 12:16:43.157] Server {0x7f34c3dda800} DEBUG: (cache_init)
hw_sector_size=512, size=4294967296, blocks=524288, disk_id=0/64544,
file_pathname=1
[Jun 10 12:16:43.207] Server {0x7f34c3dda800} DEBUG: (cache_init) initialized
span '/opt/trafficserver/var/trafficserver'
[Jun 10 12:16:43.207] Server {0x7f34c3dda800} DEBUG: (cache_init)
hw_sector_size=4096, size=33554432, blocks=4096, disk_id=64517/391104,
file_pathname=0
[Jun 10 12:16:43.267] Server {0x7f34c3dda800} DEBUG: (cache_init) Cache::open -
proxy.config.cache.min_average_object_size = 131072
[Jun 10 12:16:43.267] Server {0x7f34c3dda800} DEBUG: (cache_init)
CacheProcessor::cacheInitialized - theCache, total_size = 0 = 0 MB
[Jun 10 12:16:43.267] Server {0x7f34c3dda800} DEBUG: (cache_init)
CacheProcessor::cacheInitialized - failed to initialize the cache for http:
cache disabled
> On Jun 9, 2016, at 5:34 PM, James Peach <[email protected]> wrote:
>
>
>> On Jun 8, 2016, at 1:42 PM, Eric Friedrich (efriedri) <[email protected]>
>> wrote:
>>
>> Using ATS v5.3.2, I have a 1GB virtual disk configured (via OpenStack) as
>> /dev/sdb. This is the only disk in my volume. There are a few other disks in
>> another volume, but I’m not troubleshooting those yet.
>>
>> When I start ATS, I see the following in diags.log:
>>
>> [centos@beta1-edge2 ~]$ tail
>> /opt/trafficserver/var/log/trafficserver/diags.log
>> [Jun 8 20:27:05.327] Server {0x2b702a726700} WARNING: the size of volume 1
>> (0) is less than the minimum required volume size 128
>> [Jun 8 20:27:05.327] Server {0x2b702a726700} WARNING: volume 1 is not
>> created
>> [Jun 8 20:27:05.328] Server {0x2b702a726700} WARNING: failed to initialize
>> the cache for http: cache disabled
>> [Jun 8 20:27:05.328] Server {0x2b702a726700} NOTE: cache disabled
>
> It sounds like ATS wasn't able to probe the geometry for that volume. Can you
> run "traffic_server -T cache_init" and see what size it detected?
>
>>
>>
>> Is any special action needed to get ATS to recognize and begin using the
>> disks?
>>
>> Thanks!
>> Eric
>>
>>
>>
>> More details:
>> [centos@beta1-edge2 ~]$ cat
>> /opt/trafficserver/etc/trafficserver/storage.config
>> /dev/ram0 volume=2
>> /dev/ram1 volume=2
>> /dev/ram2 volume=2
>> /dev/ram3 volume=2
>> /dev/ram4 volume=2
>> /dev/ram5 volume=2
>> /dev/ram6 volume=2
>> /dev/ram7 volume=2
>> /dev/vdb volume=1
>> [centos@beta1-edge2 ~]$ sudo fdisk -l /dev/vdb
>>
>> Disk /dev/vdb: 1073 MB, 1073741824 bytes
>> 16 heads, 63 sectors/track, 2080 cylinders
>> Units = cylinders of 1008 * 512 = 516096 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk identifier: 0x00000000
>
