Powerful_Storage_Devices
差别
这里会显示出您选择的修订版和当前版本之间的差别。
| 两侧同时换到之前的修订记录 前一修订版 | |||
|
Powerful_Storage_Devices [2025/02/02 14:46] whr Correct syntax |
Powerful_Storage_Devices [2025/02/03 03:12] (当前版本) whr Correct syntax |
||
|---|---|---|---|
| 行 39: | 行 39: | ||
| ===== assistant ===== | ===== assistant ===== | ||
| - | Glad to hear you’re taking proactive steps to neutralize your disc-launching death drive! 🦺 While we wait for the manufacturer to replace your physics-defying hardware, here’s a survival guide for future interactions with *any* hardware (just in case): | + | Glad to hear you’re taking proactive steps to neutralize your disc-launching death drive! 🦺 While we wait for the manufacturer to replace your physics-defying hardware, here’s a survival guide for future interactions with //any// hardware (just in case): |
| ---- | ---- | ||
| 行 133: | 行 133: | ||
| ==== Why This Matters ==== | ==== Why This Matters ==== | ||
| - | * **Driver/Firmware Synergy**: Hardware that blindly trusts commands is a liability. Drives *should* validate critical SCSI fields (e.g., "is this ejection force physically possible?"). | + | * **Driver/Firmware Synergy**: Hardware that blindly trusts commands is a liability. Drives //should// validate critical SCSI fields (e.g., "is this ejection force physically possible?"). |
| * **Endianness Awareness**: Cross-platform drivers must always handle byte order, even in 2024. Big-endian isn’t dead (network protocols, embedded systems)! | * **Endianness Awareness**: Cross-platform drivers must always handle byte order, even in 2024. Big-endian isn’t dead (network protocols, embedded systems)! | ||
| 行 414: | 行 414: | ||
| ==== Recovery and Liability ==== | ==== Recovery and Liability ==== | ||
| - | * **Sue the manufacturer**: Argue that supporting ''2000000000 RPM'' violates the *Laws of Thermodynamics Act*. | + | * **Sue the manufacturer**: Argue that supporting ''2000000000 RPM'' violates the //Laws of Thermodynamics Act//. |
| * **Salvage data**: Use ''dd_rescue'' on the disk remnants, but wear a hazmat suit. | * **Salvage data**: Use ''dd_rescue'' on the disk remnants, but wear a hazmat suit. | ||
| * **Migrate to the cloud**: Let AWS/Azure deal with spinning rust. | * **Migrate to the cloud**: Let AWS/Azure deal with spinning rust. | ||
| 行 458: | 行 458: | ||
| ==== 2. SSD/NVMe Selection Guidelines ==== | ==== 2. SSD/NVMe Selection Guidelines ==== | ||
| - | === For General Use**: === | + | === For General Use: === |
| * **Enterprise-Grade SSDs**: Prioritize drives with power-loss protection (PLP) and high endurance (DWPD/TBW ratings). | * **Enterprise-Grade SSDs**: Prioritize drives with power-loss protection (PLP) and high endurance (DWPD/TBW ratings). | ||
| * Example: Samsung PM1735, Intel D5-P5316, or Micron 9400 MAX. | * Example: Samsung PM1735, Intel D5-P5316, or Micron 9400 MAX. | ||
| 行 554: | 行 554: | ||
| * **Physical tape ejection**: Some drives use spring-loaded mechanisms (less violent than optical discs, but still a risk). | * **Physical tape ejection**: Some drives use spring-loaded mechanisms (less violent than optical discs, but still a risk). | ||
| - | **Verdict**: Trust, but verify. Tape drives are enterprise-grade and predictable *if* properly managed. Proceed with the steps below. | + | **Verdict**: Trust, but verify. Tape drives are enterprise-grade and predictable //if// properly managed. Proceed with the steps below. |
| ---- | ---- | ||
| 行 1116: | 行 1116: | ||
| ===== user ===== | ===== user ===== | ||
| - | Sorry to inform you, none of your **tar(1)** command exmaples worked, all of them result in missing option, incorrect usage error; the error message is similar to ''tar: Must specify one of -c, -r, -t, -u, -x'', and on another system, ''tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options''; this indicate that your **tar(1)** command examples are definitely wrong. | + | Sorry to inform you, none of your **tar(1)** command exmaples worked, all of them result in missing option, incorrect usage error; the error message is similar to ''<nowiki>tar: Must specify one of -c, -r, -t, -u, -x</nowiki>'', and on another system, ''<nowiki>tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options</nowiki>''; this indicate that your **tar(1)** command examples are definitely wrong. |
| The **tar(1)** versions I tried are: | The **tar(1)** versions I tried are: | ||
| <code> | <code> | ||
Powerful_Storage_Devices.txt · 最后更改: 2025/02/03 03:12 由 whr
除额外注明的地方外，本维基上的内容按下列许可协议发布： CC Attribution-Share Alike 4.0 International
