linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Premature ENOSPC only with zlib Compression
Date: Thu, 16 Feb 2012 21:31:35 +1100	[thread overview]
Message-ID: <201202162131.38463.chris@csamuel.org> (raw)
In-Reply-To: <CAFDW0jLfLtEpnijsratvGho8RzC9D7nJD8H2y0SdZ6AxYeGpYw@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 585 bytes --]

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 ?

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]

  reply	other threads:[~2012-02-16 10:31 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 [this message]
2012-02-16 15:05     ` Ahmet Inan
2012-02-16 17:55       ` Chris Mason
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=201202162131.38463.chris@csamuel.org \
    --to=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 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).