From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS crash on mount with 3.4.4
Date: Tue, 31 Jul 2012 18:01:04 -0700 [thread overview]
Message-ID: <20120801010104.GA7089@merlins.org> (raw)
In-Reply-To: <20120731180412.GA10520@merlins.org>
On Tue, Jul 31, 2012 at 11:04:12AM -0700, Marc MERLIN wrote:
> My kernel crashed for some other reason, and now I can't mount my btrfs
> filesystem.
> I don't care about the data, it's backed up.
>
> I'll compile a 3.5 kernel, but is there any info you'd like off that
> filesystem to see why btrfs is crashing on mount?
On the plus side, 3.5 mounted the filesystem:
[ 183.069179] device label btrfs_pool1 devid 1 transid 20769 /dev/mapper/test
[ 183.087805] btrfs: disk space caching is enabled
[ 183.224784] btrfs: no dev_stats entry found for device /dev/mapper/test (devid 1) (OK on first mount after mkfs)
[ 186.277795] Btrfs detected SSD devices, enabling SSD mode
[ 188.477443] btrfs: unlinked 6 orphans
[ 188.477451] btrfs: truncated 1 orphans
[ 411.837015] btrfs: unlinked 13 orphans
[ 414.373500] btrfs: unlinked 35 orphans
This seems to hint that I lost random files and that I don't know what they are.
I suppose I can go back to my latest hourly snapshot which is more likely to not have
truncated or missing files.
Is there anything else someone would want off that filesystem that will help
the developers?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2012-08-01 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 18:04 BTRFS crash on mount with 3.4.4 Marc MERLIN
2012-08-01 1:01 ` Marc MERLIN [this message]
2012-08-01 5:13 ` cwillu
2012-08-02 13:40 ` David Sterba
2012-08-02 14:26 ` Marc MERLIN
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=20120801010104.GA7089@merlins.org \
--to=marc@merlins.org \
--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).