You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "David Robinson (JIRA)" <ji...@apache.org> on 2011/02/08 02:10:57 UTC
[jira] Created: (TS-667) Ability to keep traffic server from
initializing the wrong disks when using RAW disk mode.
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
Priority: Minor
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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-667) Ability to keep traffic server from
initializing the wrong disks when using RAW disk mode.
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-667:
-----------------------------
Fix Version/s: (was: 2.1.7)
2.1.8
> 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
> Priority: Minor
> Labels: features
> Fix For: 2.1.8
>
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-667) Ability to keep traffic server from
initializing the wrong disks when using RAW disk mode.
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-667:
-----------------------------
Fix Version/s: (was: 2.1.8)
3.1
> 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
> Priority: Minor
> Labels: features
> Fix For: 3.1
>
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-667) Ability to keep traffic server from
initializing the wrong disks when using RAW disk mode.
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102328#comment-13102328 ]
Leif Hedstrom commented on TS-667:
----------------------------------
This is still a good idea, however, John Plevyak pointed out an "easy" workaround, at least on Linux, where there are multiple ways to find the raw device. In my case, I can use either of
/dev/sdd
/dev/disk/by-id/ata-Maxtor_6B300S0_B612SBPH
/dev/disk/by-path/pci-0000:06:00.0-scsi-1:0:0:0
The first one of course is problematic, because it can change at any time if the kernel so decides. But the last two ought to uniquely identify the disk (or a partition within the disk, at least in the case of by-id).
> 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
> Priority: Minor
> Labels: features
> Fix For: 3.1.2
>
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-667) Ability to keep traffic server from
initializing the wrong disks when using RAW disk mode.
Posted by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-667:
-----------------------------
Fix Version/s: (was: 3.1.2)
3.2.0
> 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
> Priority: Minor
> Labels: features
> Fix For: 3.2.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 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
[jira] Updated: (TS-667) Ability to keep traffic server from
initializing the wrong disks when using RAW disk mode.
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-667:
-----------------------------
Fix Version/s: 2.1.7
> 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
> Priority: Minor
> Labels: features
> Fix For: 2.1.7
>
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira