public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	"hugh@veritas.com" <hugh@veritas.com>,
	"npiggin@suse.de" <npiggin@suse.de>,
	"riel@redhat.com" <riel@redhat.com>,
	"lee.schermerhorn@hp.com" <lee.schermerhorn@hp.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs BUG on creating huge sparse file
Date: Wed, 29 Apr 2009 19:45:26 +0800	[thread overview]
Message-ID: <20090429114526.GA24418@localhost> (raw)
In-Reply-To: <1241005222.19174.1.camel@think.oraclecorp.com>

On Wed, Apr 29, 2009 at 07:40:22PM +0800, Chris Mason wrote:
> On Wed, 2009-04-29 at 16:21 +0800, Wu Fengguang wrote:
> > On Wed, Apr 29, 2009 at 04:16:16PM +0800, Wu Fengguang wrote:
> > > On Thu, Apr 09, 2009 at 10:37:39AM -0400, Chris Mason wrote:
> > [snip]
> > > > PagePrivate is very common.  try_to_releasepage failing on a clean page
> > > > without the writeback bit set and without dirty/locked buffers will be
> > > > pretty rare.
> > > 
> > > Yup. btrfs seems to tag most(if not all) dirty pages with PG_private.
> > > While ext4 won't.
> > 
> > Chris, I run into a btrfs BUG() when doing
> > 
> >         dd if=/dev/zero of=/b/sparse bs=1k count=1 seek=104857512345
> > 
> > The half created sparse file is
> > 
> >         -rw-r--r-- 1 root root 98T 2009-04-29 14:54 /b/sparse
> >         Or
> >         -rw-r--r-- 1 root root 107374092641280 2009-04-29 14:54 /b/sparse
> > 
> > Below is the kernel messages. I can test patches you throw at me :-)
> > 
> 
> How big was the FS you were testing this on?  It works for me...

df says:

/dev/sda3             4.3G   28K  4.3G   1% /b

Oh bad, I cannot reproduce it now..

Thanks,
Fengguang

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2009-04-29 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090407509.382219156@firstfloor.org>
     [not found] ` <20090407151010.E72A91D0471@basil.firstfloor.org>
     [not found]   ` <1239210239.28688.15.camel@think.oraclecorp.com>
     [not found]     ` <20090409072949.GF14687@one.firstfloor.org>
     [not found]       ` <20090409075805.GG14687@one.firstfloor.org>
     [not found]         ` <1239283829.23150.34.camel@think.oraclecorp.com>
     [not found]           ` <20090409140257.GI14687@one.firstfloor.org>
     [not found]             ` <1239287859.23150.57.camel@think.oraclecorp.com>
     [not found]               ` <20090429081616.GA8339@localhost>
2009-04-29  8:21                 ` btrfs BUG on creating huge sparse file Wu Fengguang
2009-04-29 11:40                   ` Chris Mason
2009-04-29 11:45                     ` Wu Fengguang [this message]

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=20090429114526.GA24418@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=chris.mason@oracle.com \
    --cc=hugh@veritas.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=riel@redhat.com \
    --cc=x86@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