From: Martin Steigerwald <martin@lichtvoll.de>
To: Maximilian Eschenbacher <maximilian@eschenbacher.email>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Stability of Btrfs in Kernel 3.0
Date: Thu, 04 Jun 2015 15:55:49 +0200 [thread overview]
Message-ID: <15093386.MD5Tv7KU3x@merkaba> (raw)
In-Reply-To: <20150604125448.GB3626@kajt.de>
Am Donnerstag, 4. Juni 2015, 14:54:48 schrieb Maximilian Eschenbacher:
> Greetings,
>
> I am wondering about the stability of btrfs in this kernel version since
> Negear ist selling those ReadyNAS with a buttload of features including
> btrfs and linux kernel 3.0.
>
> Is this a system one can use to keep backup? Do you have any suggestions
> on what operations may be cause problems or how to keep btrfs happy and
> running?
BTRFS and Kernel 3.0?
Unless its has a newer BTRFS version or at least critical fixed backported, I
would run away from it.
Free space management in Kernel 3.0 still had issues that even with 2 GiB
free the filesystem could report its full, while also denying to rm a file,
delete a subvolume or do anything else to mitigate the situation. I have
seen this on SLES 11 SP 3.
I suggest something newer. Really.
Or, if you still want to use it:
If you want to store 50 GiB, keep 50 GiB of space free, or at least 20-30
GiB. I.e. have plenty of free space on the device. Do not fill up the
filesystem.
Or well… use another filesystem on that device.
In addition meanwhile there will be a ton of other issues with such an old
BTRFS fixed.
So until you can´t get a newer kernel for that device, I would not use it
with BRFS.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2015-06-04 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 12:54 Stability of Btrfs in Kernel 3.0 Maximilian Eschenbacher
2015-06-04 13:55 ` Martin Steigerwald [this message]
2015-06-04 15:33 ` Maximilian Eschenbacher
2015-06-04 16:31 ` Justin Maggard
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=15093386.MD5Tv7KU3x@merkaba \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=maximilian@eschenbacher.email \
/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