From: Adrian Bastholm <adrian@javaguru.org>
To: quwenruo.btrfs@gmx.com, linux-btrfs@vger.kernel.org
Subject: Re: btrfs problems
Date: Mon, 17 Sep 2018 13:55:05 +0200 [thread overview]
Message-ID: <CAMrg+aTtyOSOnZMj+4q13f7pv9wMydFgTDZ5KLbQSRz8HHcbKw@mail.gmail.com> (raw)
In-Reply-To: <ecac52ad-70ed-e0e3-5660-1717f0d4f5e0@gmx.com>
> Well, I'd say Debian is really not your first choice for btrfs.
> The kernel is really old for btrfs.
>
> My personal recommend is to use rolling release distribution like
> vanilla Archlinux, whose kernel is already 4.18.7 now.
I just upgraded to Debian Testing which has the 4.18 kernel
> Anyway, enjoy your stable fs even it's not btrfs anymore.
My new stable fs is too rigid. Can't grow it, can't shrink it, can't
remove vdevs from it , so I'm planning a comeback to BTRFS. I guess
after the dust settled I realize I like the flexibility of BTRFS.
This time I'm considering BTRFS as rootfs as well, can I do an
in-place conversion ? There's this guide
(https://www.howtoforge.com/how-to-convert-an-ext3-ext4-root-file-system-to-btrfs-on-ubuntu-12.10)
I was planning on following.
Another thing is I'd like to see a "first steps after getting started
" section in the wiki. Something like take your first snapshot, back
up, how to think when running it - can i just set some cron jobs and
forget about it, or does it need constant attention, and stuff like
that.
BR Adrian
--
Vänliga hälsningar / Kind regards,
Adrian Bastholm
``I would change the world, but they won't give me the sourcecode``
next prev parent reply other threads:[~2018-09-17 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 13:58 btrfs problems Adrian Bastholm
2018-09-16 14:50 ` Qu Wenruo
[not found] ` <CAMrg+aTNK1cBG7rGVfudpydD6hMJz9UW0-3mdS8Yx4tqAQZE6Q@mail.gmail.com>
2018-09-16 20:11 ` Fwd: " Adrian Bastholm
2018-09-16 20:54 ` Chris Murphy
[not found] ` <ecac52ad-70ed-e0e3-5660-1717f0d4f5e0@gmx.com>
2018-09-17 11:55 ` Adrian Bastholm [this message]
2018-09-17 12:44 ` Qu Wenruo
2018-09-17 12:59 ` Stefan K
2018-09-20 17:23 ` Adrian Bastholm
2018-09-20 19:39 ` Chris Murphy
2018-09-20 21:35 ` Adrian Bastholm
2018-09-20 22:15 ` Chris Murphy
2018-09-20 22:21 ` Remi Gauvin
2018-09-22 6:49 ` Duncan
2018-09-16 18:35 ` Chris Murphy
[not found] ` <CAMrg+aQw-sjXpaff=cS6X2-CWDRfOy1f8orQsEsy48xrsuPe3g@mail.gmail.com>
2018-09-16 20:12 ` Fwd: " Adrian Bastholm
[not found] ` <CAJCQCtQPniv4eJSsbT24bma9Gv6_T44zoq9owSYmPNmKO7hXaA@mail.gmail.com>
2018-09-16 20:13 ` Adrian Bastholm
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=CAMrg+aTtyOSOnZMj+4q13f7pv9wMydFgTDZ5KLbQSRz8HHcbKw@mail.gmail.com \
--to=adrian@javaguru.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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).