From: Markus Suvanto <markus.suvanto@gmail.com>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/delayed-inode.c:1693!
Date: Tue, 26 Jul 2011 11:01:41 +0300 [thread overview]
Message-ID: <CAA_Wi2L3n+t8fjc=z7Ei0Py-7VoFE73MQsnQvDsgVayfLKL78w@mail.gmail.com> (raw)
In-Reply-To: <CAE5mzvisUva+TdisJbJ7dfx2Ky1FUibAgCZ42GeNtHkBAjN-XA@mail.gmail.com>
=46ilesystem is almost empty:
/dev/mapper/vg_md1-btrfs
155G 2,1G 152G 2% /mnt/btrfs
=46ile system is made using command
mkfs.btrfs /dev/mapper/vg_md1-btrfs
If you can't reproduce this I can try to compile kernel
using debug stuff....
-Markus
2011/7/26 cwillu <cwillu@cwillu.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.)
>>
>> 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
next prev parent reply other threads:[~2011-07-26 8:01 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
2011-07-26 8:01 ` Markus Suvanto [this message]
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='CAA_Wi2L3n+t8fjc=z7Ei0Py-7VoFE73MQsnQvDsgVayfLKL78w@mail.gmail.com' \
--to=markus.suvanto@gmail.com \
--cc=cwillu@cwillu.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.