...on Wed, Feb 21, 2018 at 09:08:15AM -0500, Hendrik Boom wrote:
> Laast I heard here about btrfs is that it's recommended for use only bu
> those who "know where the bodies are buried".
I've been running btrfs for years now, both on distribution
kernels and on newer ones I built myself. The m
Martin Steigerwald [2018-02-21 16:26]:
> My short recommendation: Do not use BTRFS with Linux 3.10.
Or more likely, don't use 3.10 at all.
Support ended in November last year.
--
Hilsen Harald
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglis
Hello Hendrik.
Hendrik Boom - 21.02.18, 15:08:
> Now I have the fortune or misfortune (I don't know which yet) to have
> a GnuBee 2, waiting in its box to be assembled. The online page
> https://lwn.net/Articles/743609/ tells me that it works with kernel
> "Linux 3.10.14 with lots of changes", an
On Sat, Aug 13, 2016 at 02:26:13PM -0400, Hendrik Boom wrote:
> > For anything that can break your system, and for running unstable, btrfs is
> > awesome. You can make snapshots at any point (most people have at least a
> > daily cronjob), and then restore or mount live when you want. And when yo
Quite frankly, I would not overly concern myself with Lennart's
Poettering's opinion.
He has been quoted: "Open Source community is full of assholes, and I
probably more than most others am one of their most favourite targets."
That's probably true in many ways. I've seen plenty of them, how
On 02/22/2015 07:28 PM, Jim Murphy wrote:
> [...]
> Part of the discussion:
>
>>> btrfs checksumming theoretically allows you to transparently recover
>>> after media corruption if filesystem has redundancy (more than one
>>> copy of data). Journald checksum will probably detect corruption, but
>>>
