From: Chris Mason <chris.mason@oracle.com>
To: Bron Gondwana <brong@fastmail.fm>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Bug Report - crash copying in large file
Date: Mon, 9 Jun 2008 06:08:22 -0400 [thread overview]
Message-ID: <20080609060822.6a301f59@think.oraclecorp.com> (raw)
In-Reply-To: <20080606112251.GA20143@brong.net>
On Fri, 6 Jun 2008 21:22:51 +1000
Bron Gondwana <brong@fastmail.fm> wrote:
> > Yes, this was definitely an ENOSPC oops. Sorry, I do plan on
> > starting on enospc, it will come right after the tree concurrency.
>
> Hey, I really don't care that much - I have a duplicate sitting on
> reiserfs on the next partition over, and rsync frequently enough
> that re-fetching from IMAP won't hurt much.
>
> Anything I can do (with my limited FS experience) to help
> with ENOSPC?
I'm afraid there isn't a simple solution for enospc, it is going to be
a long process to nail down all the corners. If you're interested in
projects, http://btrfs.wiki.kernel.org/index.php/Project_ideas is a
better place to start.
-chris
prev parent reply other threads:[~2008-06-09 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 4:15 Bug Report - crash copying in large file Bron Gondwana
2008-06-05 12:25 ` Chris Mason
2008-06-06 11:22 ` Bron Gondwana
2008-06-09 10:08 ` Chris Mason [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=20080609060822.6a301f59@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=brong@fastmail.fm \
--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.