From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: possible bug in balance
Date: Sat, 3 Jan 2015 10:30:30 +0000 (UTC) [thread overview]
Message-ID: <pan$e75b1$a4dba2e8$4e6523ad$73f0cde8@cox.net> (raw)
In-Reply-To: 1256750348.24201420209749292.JavaMail.root@shiva
luvar posted on Fri, 02 Jan 2015 15:42:29 +0100 as excerpted:
> root@blackdawn:/home/luvar# uname -a
> [...] 3.13.0-30-generic [...]
>
> root@blackdawn:/home/luvar# btrfs v
> Btrfs v0.20-rc1-189-g704a08c
>
>
> Am I doing something forbidden [...]
Those versions are your problem. Do you know how fast btrfs is
improving, how old those are (hint, there are about five kernel release
series a year and we're now on the 3.19 development series with 3.18
stable, so 3.13 is... about five releases back and thus about a year old!
), and how many bugs have been fixed since then?
Try something newer than the paleolithic age, say a current 3.18.x stable
series kernel or a 3.19-rc, and the recent btrfs-progs 3.18.0, and you
should see rather better results. There are valid reasons to stick to
old and stable, but they simply don't mix well with a new and still not
completely stable filesystem that still sees regular bug fixes, and not
just for code introduced in the last kernel, either! Therefore, if you
want old and stable, choose a different filesystem; while if you want to
run btrfs, staying current is strongly recommended.
Meanwhile, if you haven't yet, you may want to spend some time on the
wiki reading up. Take a look at the stuff under section 5.1, Guides and
usage information, especially. It'll answer a lot of questions and could
save your data too. =:^)
https://btrfs.wiki.kernel.org
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-01-03 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1377898232.24181420209516734.JavaMail.root@shiva>
2015-01-02 14:42 ` possible bug in balance luvar
2015-01-03 10:30 ` Duncan [this message]
2015-01-04 10:39 ` Erkki Seppala
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='pan$e75b1$a4dba2e8$4e6523ad$73f0cde8@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 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.