| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
| |
I had this in my local configuration.nix since a while and while it
might be annoying when this runs every month, I think it's better to do
it regularily rather than having a dying disk go unnoticed.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
This reverts commit 292099429d0bab51f0cb634c6bc5c9745c4c1383.
Well, looks like iwd ist still not ready for primetime with my
university's eduroam implementation.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Now, it's not yet clear if iwd will work with my uni's eduroam service
at all. Either way though, this is in preparation for the switch and
test once I'm near an eduroam access point.
|
| |
|
|
|
|
|
|
| |
Since quite a while, NixOS re-uses the passphrases from earlier devices,
so there is no need anymore for such a device in order to unlock
multiple containers with the same passphrase.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
| |
The "luksClose" subcommand for cryptsetup has been deprecated for a
while, so let's move over to "close".
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since I got a new SSD for the machine (thanks @cvdnext), I also had the
opportunity to re-create my LUKS containers to LUKS2 with Argon2 key
derivation alongside creating bcache backing devices.
The change in order to support bcache is just a matter of adding
"bcache" to availableKernelModules and we're done.
However, as the storage configuration is not a very common one, I
decided to add a test specific to that to make sure future NixOS updates
won't prevent the machine from booting.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
| |
Remove unused packages and commented out stuff.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Since alot version 0.8, Python 2.x is no longer supported and
subsequently trying to use it from pythonPackages will result in an
evaluation error.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The internal SSD of the machine just died, so I reconstructed the Nix
store on the spinning rust from the machine configuration and we're now
left without the SSD.
Maybe it makes sense to still use the SSD with bcache, depending on how
failure-resilient it is, but for now, let's just remove it so we at
least have a working system.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
| |
These packages are unnecessary currently.
|
| |
|
|
| |
both don't exist anymore
|
| |
|
|
| |
TLP is running, so this won't work.
|
| |
|
|
|
|
| |
I've become increasingly aware that my configurations drift, and while
this is still not amazing in terms of DRY and whatnot, it's all I can do
for now.
|
| |
|
|
|
|
|
|
|
|
|
| |
The upstream version 0.6.4 was released 2 months ago and it recently hit
nixpkgs[1], so we can finally drop the override as the new version now
contains the fix[2] for the problem that affected me.
[1]: https://github.com/NixOS/nixpkgs/commit/5e2590ba6fd352bc65b4cd7fd82
[2]: https://github.com/gpodder/podcastparser/pull/17
Signed-off-by: aszlig <aszlig@nix.build>
|
| | |
|
| |
|
|
| |
Everything is on neomutt now so there is no need for thunderbird.
|
| | |
|
| |
|
|
|
|
|
| |
I've set up a RPi to act as a print server, but the printers are
configured as RAW, so the burden of having the correct drivers installed
lies with the client, which is fine considering the current network
setup.
|
| |
|
|
|
|
|
|
| |
User is likely to switch, so let's add Firefox alongside to Chromium and
eventually remove Chromium at some day.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @dwenola
|
| |
|
|
|
| |
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @dwenola
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@402ee4e9eaf08a697672718cd502067c726a7c73, mpv by
itself no longer has a script argument but there is now
"mpv-with-scripts", which boils down to something similar.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch, @sternenseemann
|
| |
|
|
|
|
|
|
| |
The users.extraUsers has been renamed a long time ago, so let's switch
to the new option.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @sternenseemann
|
| | |
|
| | |
|
| |
|
|
| |
The namespace was kind of hard to remember, so let’s just call it openlab.
|
| |
|
|
| |
The machine’s mainboard broke, so it’s gone.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
