From: Chris Mason <chris.mason@oracle.com>
To: Ahmet Inan <ainan@mathematik.uni-freiburg.de>
Cc: Chris Samuel <chris@csamuel.org>, linux-btrfs@vger.kernel.org
Subject: Re: Premature ENOSPC only with zlib Compression
Date: Thu, 16 Feb 2012 12:55:36 -0500 [thread overview]
Message-ID: <20120216175536.GL21896@shiny> (raw)
In-Reply-To: <CAFDW0jJgNxNXJHiJxur+QaPAioyAyZ+-ftnTtZ2rR69Tqy0bfw@mail.gmail.com>
On Thu, Feb 16, 2012 at 04:05:40PM +0100, Ahmet Inan wrote:
> On Thu, Feb 16, 2012 at 11:31 AM, Chris Samuel <chris@csamuel.org> wrote:
> > On Thursday 16 February 2012 19:06:52 Ahmet Inan wrote:
> >
> >> and got ENOSPC again :(
> >>
> >> so it doesnt matter if lzo or zlib: ENOSPC with compression
> >> enabled!
> >>
> >> my kernel: vanilla 3.2.5
> >
> > I know that there has been an ENOSPC fix go in to the 3.3 RC kernels
> > since the 3.2 release, any chance you'd be able to see if it still
> > happens with the current 3.3 RC ?
>
> just tested 3.3.0-rc3, and it works like a charm!
>
> but there are lots of issues with external packages not compiling with 3.3,
> why i wont be able to deploy it to our systems here yet.
>
> could this one bugfix be backported to 3.2?
All of the btrfs patches in 3.3-rc are against 3.2 in my git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
>
> here are some results from my unsquashfs'ing just to show how
> awesome btrfs with lzo is. these results are _not_ from an ssd btw!
> (spinning disks, rebooted between tests)
Very nice ;)
-chris
next prev parent reply other threads:[~2012-02-16 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 16:13 Premature ENOSPC only with zlib Compression Mitch Harder
2012-01-20 18:55 ` Ahmet Inan
2012-02-08 21:01 ` Mitch Harder
2012-02-09 2:14 ` Liu Bo
2012-02-09 20:29 ` Mitch Harder
2012-02-16 8:06 ` Ahmet Inan
2012-02-16 10:31 ` Chris Samuel
2012-02-16 15:05 ` Ahmet Inan
2012-02-16 17:55 ` Chris Mason [this message]
2012-02-17 16:34 ` Ahmet Inan
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=20120216175536.GL21896@shiny \
--to=chris.mason@oracle.com \
--cc=ainan@mathematik.uni-freiburg.de \
--cc=chris@csamuel.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 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.