[TS-667] Ability to keep traffic server from initializing the wrong disks when using RAW disk mode.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 6.0.0
• Component/s: Cache, Configuration
• Labels: A features
• Assignee: Crystal Qian
• Reporter: David Robinson
• Created: 08/Feb/11 01:09
• Updated: 04/Feb/16 18:55
• Resolved: 13/Jun/15 03:45

Description

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

Issue Links

• relates to: TS-3165 Cache Toolkit API