From: Adam Borowski <kilobyte@angband.pl>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Steven Haigh <netwiz@crc.id.au>, linux-btrfs@vger.kernel.org
Subject: Re: compress=lzo safe to use? (was: Re: Trying to rescue my data :()
Date: Sun, 11 Sep 2016 22:06:35 +0200 [thread overview]
Message-ID: <20160911200635.GA19703@angband.pl> (raw)
In-Reply-To: <4096253.hu8ZAHGEqT@merkaba>
On Sun, Sep 11, 2016 at 09:48:35PM +0200, Martin Steigerwald wrote:
> Hmm… I found this from being referred to by reading Debian wiki page on
> BTRFS¹.
>
> I use compress=lzo on BTRFS RAID 1 since April 2014 and I never found an
> issue. Steven, your filesystem wasn´t RAID 1 but RAID 5 or 6?
>
> I just want to assess whether using compress=lzo might be dangerous to use in
> my setup. Actually right now I like to keep using it, since I think at least
> one of the SSDs does not compress. And… well… /home and / where I use it are
> both quite full already.
>
> [1] https://wiki.debian.org/Btrfs#WARNINGS
I have used compress=lzo for years, kernels 3.8, 3.13 and 3.14 (a bunch of
machines), without a single glitch; heavy snapshotting, single dev only, no
quota. Until recently I did never balanced.
I did have a case of ENOSPC with <80% full on 4.7 which might or might not
be related to compress=lzo.
--
Second "wet cat laying down on a powered-on box-less SoC on the desk" close
shave in a week. Protect your ARMs, folks!
next prev parent reply other threads:[~2016-09-11 20:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:52 Trying to rescue my data :( Steven Haigh
2016-06-24 16:26 ` Steven Haigh
2016-06-24 16:59 ` ronnie sahlberg
2016-06-24 17:05 ` Steven Haigh
2016-06-24 17:40 ` Austin S. Hemmelgarn
2016-06-24 17:43 ` Steven Haigh
2016-06-24 17:50 ` Austin S. Hemmelgarn
2016-06-25 4:19 ` Steven Haigh
2016-06-25 16:25 ` Chris Murphy
2016-06-25 16:39 ` Steven Haigh
2016-06-25 17:14 ` Chris Murphy
2016-06-26 2:30 ` Duncan
2016-06-26 3:13 ` Steven Haigh
2016-09-11 19:48 ` compress=lzo safe to use? (was: Re: Trying to rescue my data :() Martin Steigerwald
2016-09-11 20:06 ` Adam Borowski [this message]
2016-09-11 20:27 ` Chris Murphy
2016-09-11 20:49 ` compress=lzo safe to use? Hans van Kranenburg
2016-09-12 4:36 ` Duncan
2016-09-17 9:30 ` Kai Krakow
2016-09-12 1:00 ` Steven Haigh
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=20160911200635.GA19703@angband.pl \
--to=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=netwiz@crc.id.au \
/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.