[
https://issues.apache.org/jira/browse/TS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584427#comment-14584427
]
ASF subversion and git services commented on TS-667:
----------------------------------------------------
Commit 5103e1e643fa9429d42a876e260b20c8c2e549e3 in trafficserver's branch
refs/heads/master from [~psudaemon]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=5103e1e ]
TS-667: Minor change
This closes #221
> Ability to keep traffic server from initializing the wrong disks when using
> RAW disk mode.
> ------------------------------------------------------------------------------------------
>
> Key: TS-667
> URL: https://issues.apache.org/jira/browse/TS-667
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache, Configuration
> Reporter: David Robinson
> Assignee: Crystal Qian
> Priority: Minor
> Labels: A, features
> Fix For: 6.0.0
>
>
> When disk devices are configured in storage.config for RAW mode they are
> automatically initialized when traffic server first starts up. If disk device
> names change later due to adding/removing disks or kernel changes
> trafficserver will overwrite disks that the user may not want to be cache
> disks. This leads to data loss on the affected disks.
> Maybe a feature could be added similar to squid's -z where cache disks must
> be explicitly initialized before they can be used. Or a configuration
> variable that changes trafficserver's initialization behavior.
> (6:49:06 PM) zwoop: so, maybe have a few settings for the config
> (6:49:06 PM) zwoop: 0 - Let it reinitialize cache as it likes
> (6:49:06 PM) zwoop: 1 - Only initialize cache explicitly
> (6:49:06 PM) zwoop: 2 - Only initialize cache explicitly, and refuse to start
> up if we detect a cache disk with bad header
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
