From: "Franziska Näpelt" <franziska.naepelt@hiperscan.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs crashes
Date: Wed, 10 Jul 2013 12:53:00 +0200 [thread overview]
Message-ID: <51DD3D0C.3060908@hiperscan.com> (raw)
In-Reply-To: <20130708132453.GH2260@localhost.localdomain>
I created a bug:
https://bugzilla.kernel.org/show_bug.cgi?id=60544
Am 08.07.2013 15:24, schrieb Josef Bacik:
> On Mon, Jul 08, 2013 at 08:46:17AM +0200, Franziska Näpelt wrote:
>> Hi everybody,
>>
>> we are using a btrfs RAID 1 with four 2TB hard drives on a Debian 7.1
>> (Kernel 3.9.6).
>>
>> After about one year of working, there was an error in messages log and the
>> filesystem was mounted read-only.
>>
>> After that I restarted the system but that doesn't fix the bug. The
>> btrfs-filesystem couldn't be mounted.
>>
>> I attach four logs:
>>
>> -> when the error occured
>> -> after the error occured
>> -> when rebooting the system
>> -> when I tried ti mount manually
>>
>> Before I rebuilt the filesystem (formatting everything and creating a new
>> btrfs-pool) I made a btrfs-image. I can provide it to you.
>>
>
> Can you file a bugzilla at bugzilla.kernel.org (make sure the component is set
> to btrfs) with all of this information and a link to the image, and the output
> of btrfsck? Please use the most recent version of btrfs-progs
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
>
> Thanks,
>
> Josef
> --
> 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:[~2013-07-10 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 6:46 btrfs crashes Franziska Näpelt
2013-07-08 13:24 ` Josef Bacik
2013-07-10 10:53 ` Franziska Näpelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-29 19:30 Helmut Hullen
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=51DD3D0C.3060908@hiperscan.com \
--to=franziska.naepelt@hiperscan.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 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).