From: Stephan von Krawczynski <skraw.ml@ithnet.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: My first attempt to use btrfs failed miserably
Date: Sun, 2 Feb 2020 14:22:46 +0100 [thread overview]
Message-ID: <20200202142246.1f4c36e3@ithnet.com> (raw)
In-Reply-To: <cd628b1f-25b7-0f3b-0b31-2122acdfcd36@gmx.com>
On Sun, 2 Feb 2020 20:56:20 +0800
Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> On 2020/2/2 下午8:45, Skibbi wrote:
> > Hello,
> > So I decided to try btrfs on my new portable WD Password Drive
> > attached to Raspberry Pi 4. I created GPT partition, created luks2
> > volume and formatted it with btrfs. Then I created 3 subvolumes and
> > started copying data from other disks to one of the subvolumes. After
> > writing around 40GB of data my filesystem crashed. That was super fast
> > and totally discouraged me from next attempts to use btrfs :(
> > But I would like to help with development so before I reformat my
> > drive I can help you identifying potential issues with this filesystem
> > by providing some debugging info.
> >
> > Here are some details:
> >
> > root@rpi4b:~# uname -a
> > Linux rpi4b 4.19.93-v7l+ #1290 SMP Fri Jan 10 16:45:11 GMT 2020 armv7l
> > GNU/Linux
>
> Pretty old kernel, nor recently enough backports.
Exactly this kind of answer made me leave btrfs and never come back again.
4.19.93 is not very far away from the _latest_ longterm kernel released (which
is 4.19.101).
What you are saying here is that there is no stable working btrfs in longterm
kernels at all.
Hear, hear.
My advice to the OP: use ZFS. Great performance, absolutely stable, no crash
in years.
--
Regards,
Stephan
next prev parent reply other threads:[~2020-02-02 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 12:45 My first attempt to use btrfs failed miserably Skibbi
2020-02-02 12:56 ` Qu Wenruo
2020-02-02 13:22 ` Stephan von Krawczynski [this message]
2020-02-02 20:04 ` Chris Murphy
2020-02-02 13:29 ` Martin Raiber
2020-02-02 13:36 ` Qu Wenruo
2020-02-02 14:14 ` Roman Mamedov
2020-02-02 14:45 ` Swâmi Petaramesh
2020-02-02 23:34 ` Zygo Blaxell
2020-02-03 6:28 ` Skibbi
2020-02-03 16:12 ` Chris Murphy
2020-02-03 19:01 ` Marc Joliet
2020-02-03 7:00 ` Swâmi Petaramesh
2020-02-02 19:56 ` Chris Murphy
2020-02-03 6:38 ` Skibbi
2020-02-03 6:51 ` Qu Wenruo
2020-02-03 8:42 ` Skibbi
2020-02-03 10:10 ` Qu Wenruo
2020-02-03 10:17 ` Qu Wenruo
2020-02-03 10:56 ` Skibbi
2020-02-03 11:09 ` Qu Wenruo
2020-02-03 16:17 ` Chris Murphy
2020-02-02 19:57 ` Chris Murphy
2020-02-03 19:14 ` Achim Gratz
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=20200202142246.1f4c36e3@ithnet.com \
--to=skraw.ml@ithnet.com \
--cc=linux-btrfs@vger.kernel.org \
/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).