From: Chris Mason <chris.mason@fusionio.com>
To: Michael Schmitt <tcwardrobe@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: weird kernel-oopses while deleting files on btrfs
Date: Sun, 3 Mar 2013 18:52:43 -0500 [thread overview]
Message-ID: <20130303235243.GA26002@shiny.masoncoding.com> (raw)
In-Reply-To: <513356D5.5030301@gmail.com>
On Sun, Mar 03, 2013 at 06:57:41AM -0700, Michael Schmitt wrote:
> Hi list,
>
> some rather unexpected btrfs-oopses for my taste. I use btrfs for some
> time now (mostly on external harddisks) and these "oopses" happened
> during some simple file and folder deletion operation on that device. It
> is a luks-encrypted 80GB drive. Anything like that known? And the fs was
> created just yesterday, how come there is a message like...
>
> [91491.919358] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields.
This may be from first mount after mkfs. It depends on your tools.
>
> ... but the kernel used (3.7.3 from Debian experimental on Debian sid)
> was installed several days ago. What kind of oopses are these? As of now
> there is no real data on that device. But if there were, would I need to
> be concerned about the integrity of those files?
>
> [93283.762006] WARNING: at /build/buildd-linux_3.7.3-1~experimental.1-i386-eX5kUQ/linux-3.7.3/fs/btrfs/extent-tree.c:6297 btrfs_alloc_free_block+0xcd/0x2a4 [btrfs]()
These are not oopsen but warnings. It's an ENOSPC warning as we try to
delete the extents. It did happen sometimes in this kernel, but it is
only a warning.
-chris
next prev parent reply other threads:[~2013-03-03 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 13:57 weird kernel-oopses while deleting files on btrfs Michael Schmitt
2013-03-03 23:52 ` Chris Mason [this message]
2013-03-07 10:23 ` Michael Schmitt
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=20130303235243.GA26002@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tcwardrobe@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 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).