linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Which kernel is safe to upgrade to for btrfs?
Date: Sun, 20 May 2012 22:22:20 -0700	[thread overview]
Message-ID: <20120521052220.GD15765@merlins.org> (raw)

Hi,

I upgraded to 3.3.x lately and had no end of problems with btrfs saying my
disk was full when it was not.

I read that btrfs in 3.3.x had issue and got the recommendation to
downgrade, so I went back to 3.2.16 which works for me.

Of course, I need a newer kernel for other reasons and I can't tell which
branch is safe to upgrade to for btrfs.

Have the free space problems been fixed in 3.3.x or is the 3.4.x branch
better or should I stay with 3.2.x for safety?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

             reply	other threads:[~2012-05-21  5:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  5:22 Marc MERLIN [this message]
2012-05-21  6:00 ` Which kernel is safe to upgrade to for btrfs? Chris Samuel

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=20120521052220.GD15765@merlins.org \
    --to=marc@merlins.org \
    --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 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).