All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Josef Bacik <jbacik@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: oops in btrfs_reserve_extent (v0.16)
Date: Mon, 29 Sep 2008 11:13:32 +0300	[thread overview]
Message-ID: <48E08E2C.8080903@redhat.com> (raw)
In-Reply-To: <20080929000855.GA26676@unused.rdu.redhat.com>

Josef Bacik wrote:
> Could you try with the unstable git tree?  I just rewrote a bunch of this stuff
> and like to know if the same issue is present there.  I wouldn't recommend using
> unstable for your home directory yet tho, that code still may eat children.
> Thanks,
>   

Will try that on a virtual machine -- unfortunately I am too far 
bandwidth wise from an F9 installer.

Meanwhile I rsync'ed my /home without online resizing, using v0.16.  
Filesystem and myself both happy.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


      reply	other threads:[~2008-09-29  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 20:42 oops in btrfs_reserve_extent (v0.16) Avi Kivity
2008-09-29  0:08 ` Josef Bacik
2008-09-29  8:13   ` Avi Kivity [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=48E08E2C.8080903@redhat.com \
    --to=avi@redhat.com \
    --cc=jbacik@redhat.com \
    --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.