diff options
author | aszlig <aszlig@nix.build> | 2019-02-09 14:16:51 +0100 |
---|---|---|
committer | aszlig <aszlig@nix.build> | 2019-02-09 14:16:51 +0100 |
commit | 15008e69542774c441e388ad4c2e28a2d27f9ba0 (patch) | |
tree | f766a7ce05e3602ac01894f287d860439ef712ea /machines/README.md | |
parent | 807edf7acd83ccc2f39954174c7a0b4a82d9ed2e (diff) |
machines/dnyarri: Stop bcache during sleep/scrub
I did have a major outage this week, because I was using bcache with writeback mode on a RAID10 backing storage. Fortunately, I was able to recover 99.9% of the data (only the most recent stuff wasn't recoverable), but I certainly don't want this to happen again in the future. While I did use bcache with hibernate and writeback, the interesting part is that the caching device went bonkers after a "normal" shutdown rather than a suspend/hibernate, with "normal" being "with a bunch of kernel warnings about zswap". Also, this happened around a btrfs scrub, so the inconsistency was all over the place. So first of all, I'm now going with writaround mode rather than writeback mode for the time being. Although it's slower than writeback, the chances that I need to do such a recovery again is close to 0% with writethrough and writearound because all writes are synchronous. Second, this very change makes sure that whenever the machine goes to sleep or a scrub is started, the caching is disabled and afterwards it's re-enabled. That way we shouldn't have lots of trash on the caching device. Signed-off-by: aszlig <aszlig@nix.build>
Diffstat (limited to 'machines/README.md')
0 files changed, 0 insertions, 0 deletions