All of lore.kernel.org
 help / color / mirror / Atom feed
From: cwillu <cwillu@cwillu.com>
To: Markus Suvanto <markus.suvanto@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/delayed-inode.c:1693!
Date: Tue, 26 Jul 2011 01:57:30 -0600	[thread overview]
Message-ID: <CAE5mzvisUva+TdisJbJ7dfx2Ky1FUibAgCZ42GeNtHkBAjN-XA@mail.gmail.com> (raw)
In-Reply-To: <CAA_Wi2K7w9mwGS3LO-eEydZ3R6fSeQWOSoNz6dNMkO4w8DohsQ@mail.gmail.com>

On Tue, Jul 26, 2011 at 1:51 AM, Markus Suvanto
<markus.suvanto@gmail.com> wrote:
> This is what I get =C2=A0if I use command:
> bcp file file_copy
> I can reproduce this every time when using bcp command.
>
> Filesystem is under lvm:
> /dev/mapper/vg_md1-btrfs on /mnt/btrfs type btrfs (rw,noatime,subvol=3D=
=2E)
>
> This filesystem is created using linux-3.0 and
> mkfs.btrfs, part of Btrfs v0.19-1-g4f89b6e-dirty
>
> Ok, I don't have any kernel debug stuff there but maybe you can
> reproduce this....
>
> -Markus

Appears to be an unhandled ENOSPC error; hard to tell much else
without the debug info and the details on the volume (size, mkfs args,
etc).
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-26  7:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26  7:51 kernel BUG at fs/btrfs/delayed-inode.c:1693! Markus Suvanto
2011-07-26  7:57 ` cwillu [this message]
2011-07-26  8:01   ` Markus Suvanto
2011-07-28 18:57 Marcus Sorensen
2011-07-29  5:42 ` Li Zefan

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=CAE5mzvisUva+TdisJbJ7dfx2Ky1FUibAgCZ42GeNtHkBAjN-XA@mail.gmail.com \
    --to=cwillu@cwillu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=markus.suvanto@gmail.com \
    /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.