All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Ahmet Inan <ainan@mathematik.uni-freiburg.de>
Cc: Josef Bacik <JBacik@fusionio.com>, David Sterba <dave@jikos.cz>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: ENOSPC design issues
Date: Wed, 26 Sep 2012 09:11:43 -0400	[thread overview]
Message-ID: <20120926131143.GC2328@localhost.localdomain> (raw)
In-Reply-To: <CAFDW0jLuvH9rMisDz-Y=Y_nwxzzO5K64uixd6mAiaQRmja3izA@mail.gmail.com>

On Wed, Sep 26, 2012 at 01:55:47AM -0600, Ahmet Inan wrote:
> when testing, please also do something like this:
> 
> # create big squashfs image somewhere:
> # mksquashfs / /big.img -noappend -no-sparse -e big.img
> 
> # then unpack into fresh filesystem with (and no) compression:
> # unsquashfs -f -d /subvol /big.img
> 
> this is how i was always able to trigger ENOSPC while trying to
> make a full system installation from squashfs image.
> 
> you should also try different compression algos (i only use lzo)
> 
> btw: i was able to trigger ENOSPC with for-linus on 3.5.4 on a
> i686 Pentium M Notebook with only 1GB of Memory and
> fresh FSthis way, otherwise havent seen ENOSPC for long time.
>

Have you actually seen this problem on 3.5 with no compression?  I fixed a
problem in the 3.5 timeframe that should have fixed this for no-compression, and
then I've since fixed the compression part of it in btrfs-next.  Can you retest
with btrfs-next and see if you still see the problem?  In the meantime I'm
running mksquashfs, but it's going to take a few years to complete ;).  Thanks,

Josef 

  parent reply	other threads:[~2012-09-26 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 19:03 ENOSPC design issues Josef Bacik
2012-09-24 16:59 ` Mitch Harder
2012-09-25 16:43 ` David Sterba
2012-09-25 17:02   ` Josef Bacik
2012-09-26  7:55     ` Ahmet Inan
2012-09-26 13:00       ` Josef Bacik
2012-09-26 13:11       ` Josef Bacik [this message]
2012-09-27 15:39         ` Ahmet Inan
2012-10-01  0:00     ` David Sterba

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=20120926131143.GC2328@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=ainan@mathematik.uni-freiburg.de \
    --cc=dave@jikos.cz \
    --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.