All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maximilian Eschenbacher <maximilian@eschenbacher.email>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Stability of Btrfs in Kernel 3.0
Date: Thu, 4 Jun 2015 17:33:45 +0200	[thread overview]
Message-ID: <20150604153345.GD3626@kajt.de> (raw)
In-Reply-To: <15093386.MD5Tv7KU3x@merkaba>

Hey Martin,

On 04/06/2015 15:55:49, Martin Steigerwald wrote:
>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.

thanks for the quick and precise answer. I will find out whether Netgear
did some backporting for btrfs in their kernel and report back.

Unfortunately Netgear uses only btrfs (or zfs on some systems) and one
cannot select another fs like ext4 (which they supported on previous
systems).

Regards,

Max

  reply	other threads:[~2015-06-04 15:33 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
2015-06-04 15:33   ` Maximilian Eschenbacher [this message]
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=20150604153345.GD3626@kajt.de \
    --to=maximilian@eschenbacher.email \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.