linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Bauer <jens-lists@gpio.dk>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How robust is BTRFS?
Date: Thu, 3 Dec 2020 09:55:29 +0100	[thread overview]
Message-ID: <20201203095529220651.9e528b11@gpio.dk> (raw)
In-Reply-To: <7851285.T7Z3S40VBb@merkaba>

Hi Martin.

I'm happy to hear that you have good experience with BTRFS as well. =)
-One thing I forgot to mention is that I'm also quite impressed with Western Digital's drives; they seem to last, even under such horrible conditions I put them through. ;)

It seems, after all, that one does not *have* to learn from failure. =D


Love
Jens

On Thu, 03 Dec 2020 08:59:38 +0100, Martin Steigerwald wrote:
> Jens Bauer - 03.12.20, 03:53:11 CET:
>> After correcting the problem, I got curious and listed the statistics
>> for each partition. I had more than 100000 read/write errors PER DAY
>> for 6 months. That's around 18 million read/write-errors, caused by
>> drives turning on/off "randomly".
>> 
>> AND ALL MY FILES WERE INTACT.
> 
> Awesome! Really awesome!
> 
> I am running BTRFS on a ThinkPad T520 since at least 2014. After all 
> these initial free space related issues went away with linux 4.5 or 4.6 
> I had no issues with it anymore. In part I use BTRFS RAID 1 with an 
> mSATA SSD on the laptop and it recovered from what I believe had been 
> power loss related errors on the mSATA SSD twice already. Of course that 
> is not anywhere near the dimension of errors the filesystem you have 
> experienced.
> 
> I use it on my backup drives and I use it on my server VMs.
> 
> It works for me.
> 
> Best,
> -- 
> Martin
> 
> 

  reply	other threads:[~2020-12-03  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  2:53 How robust is BTRFS? Jens Bauer
2020-12-03  7:59 ` Martin Steigerwald
2020-12-03  8:55   ` Jens Bauer [this message]
2020-12-03 10:59 ` Qu Wenruo
2020-12-03 19:13   ` Jens Bauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201203095529220651.9e528b11@gpio.dk \
    --to=jens-lists@gpio.dk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).