From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unable to unmount filesystem (bug in kernel reported in kern.log)
Date: Mon, 5 Aug 2013 04:50:48 +0000 (UTC) [thread overview]
Message-ID: <pan$5dead$acb36a7f$5d0e094f$bd2b0353@cox.net> (raw)
In-Reply-To: 51FF0D93.80207@suse.com
Jeff Mahoney posted on Sun, 04 Aug 2013 22:27:31 -0400 as excerpted:
> On 8/4/13 6:58 PM, Alfredo Esteban wrote:
>> I tried to unmount a btrfs filesystem located in a external usb hard
>> drive. This belonged to a raid1 data and metadata filesystem mounted in
>> degraded mode.
>>
>> Unfortunately, I couldn't save the image of filesystem but I could see
>> this error in kern.log:
[snip]
>> Aug 4 02:26:06 rohan kernel: [ 3878.947184] kernel BUG at
>> /build/buildd/linux-3.2.0/fs/btrfs/inode.c:806!
>
> This is against the 3.2 kernel, which is now 19 months old and ancient
> in terms of btrfs support. Please see if you can reproduce with a more
> recent kernel. Otherwise, file a bug report with Ubuntu if they are
> doing substantial btrfs backports.
Seconded.
Also, if you're not aware of the btrfs wiki yet, you probably want to
read up on btrfs there. It stresses btrfs' development nature and the
importance of running a current kernel for btrfs testing in several
places, so the fact that you're not doing so indicates that you probably
hadn't read the wiki, and are thus likely missing out on other
potentially very useful information, as well.
https://btrfs.wiki.kernel.org/
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2013-08-05 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 22:58 Unable to unmount filesystem (bug in kernel reported in kern.log) Alfredo Esteban
2013-08-05 2:27 ` Jeff Mahoney
2013-08-05 4:50 ` Duncan [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='pan$5dead$acb36a7f$5d0e094f$bd2b0353@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).