etbe

5 ms·

31.
by etbe 5y ago
It is thick for many reasons, having separate chips for security means a bigger motherboard, having a socket for a security chip, etc. But the battery is really big, much bigger than is common for modern phones.
32.
by etbe 5y ago
The Librem5 is twice as thick as any other phone I have owned in the last 10 years. In general I agree that thicker and heavier phones would be good but in this case they seem to have already got to the upper limits of what's considere
33.
by etbe 5y ago
If you use the - option in syslogd configuration for non-synchronous writes then /var/log will be only a tiny portion of writes. If you have a mail server then the many log messages about a message delivery will have hardly any wr
34.
by etbe 5y ago
I'm not sure it makes a lot of difference unless you have hundreds of snapshots. The way changes work to BTRFS is that every change without snapshots does most of the same stuff that a change with snapshots does. If however you have ma
35.
by etbe 5y ago
In addition to cables and backplanes that have been mentioned, the entire path from RAM to PCIe to disk controller has non zero risks of errors. That said I'm pretty sure that the BTRFS errors I've seen from SSDs have all been the
36.
by etbe 5y ago
If you want to mix SSD and hard drives then you probably want bcache.
37.
by etbe 5y ago
Most things last longer than their warranty, if even 5% of an item fail to reach the warranty then it's a disaster for the manufacturer. Planning for replacement is probably a good idea when you are 5* the warranty.
38.
by etbe 5y ago
When I was using a Thinkpad X1 Carbon Gen6 with Linux it would hit a thermal limit and throttle the CPU speed if I read from NVMe at maximum speed for more than about 30 seconds. That was partly due to an issue with the way Linux and the BI
39.
by etbe 5y ago
In the post I wrote 'between the 2 SSDs SMART reports 18 uncorrectable errors and “btrfs device stats” reports 55 errors on one of them'. That's 37 errors that BTRFS found that mdadm wouldn't have found. 37 errors out of
40.
by etbe 5y ago
Sometimes that's a good idea, sometimes it might make things worse. A previous server that had a RAID-1 of SSDs was limited by SSD write speed. As the SSDs got old the write speed dropped significantly. If I had 2 servers that each had
41.
by etbe 5y ago
zram is a good thing. However in my investigations in 2014 "my conclusion was that swap wouldn’t be a problem as no normally operating systems that I run had swap using any significant fraction of total disk writes". During the la
42.
by etbe 5y ago
The "server which runs my blog (among many other things)" probably has most of it's writes from a mail server for dozens of domains and has some commercial web sites that are very interactive and database backed.