From: Hendrik Friedel <hendrik@friedels.name>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck errors is it save to fix?
Date: Thu, 07 Nov 2013 20:16:34 +0100 [thread overview]
Message-ID: <527BE712.40304@friedels.name> (raw)
In-Reply-To: <5279E581.4000700@friedels.name>
Hello again,
can someone please help me on this?
Regards,
Hendrik
Am 06.11.2013 07:45, schrieb Hendrik Friedel:
> Hello,
>
> sorry, I was totally unaware still being on 3.11rc2.
>
> I re-ran btrfsck with the same result:
> ./btrfs-progs/btrfsck /dev/sdc1
> Checking filesystem on /dev/sdc1
> UUID: 989306aa-d291-4752-8477-0baf94f8c42f
> checking extents
> checking free space cache
> checking fs roots
> root 256 inode 9579 errors 100
> root 256 inode 9580 errors 100
> root 256 inode 14258 errors 100
> root 256 inode 14259 errors 100
> root 4444 inode 9579 errors 100
> root 4444 inode 9580 errors 100
> root 4444 inode 14258 errors 100
> root 4444 inode 14259 errors 100
> found 1992865028914 bytes used err is 1
> total csum bytes: 3207847732
> total tree bytes: 3902865408
> total fs tree bytes: 38875136
> total extent tree bytes: 135864320
> btree space waste bytes: 411665032
> file data blocks allocated: 3426722545664
> referenced 3426000965632
> Btrfs v0.20-rc1-358-g194aa4a
>
>
> Now dmesg and the syslog stay clear of entries relatet to btrfs.
> But I think, that might also be a coincidence: I ran the old Kernel for
> weeks until this error came, whereas I ran this kernel merely 12h.
>
> Now:
> Does it make sense to futher try to find a possible bug, or do we
> suspect it is fixed? If so: How can I help?
>
> And:
> Can I fix these Problems safely with btrfsck?
>
> Regards,
> Hendrik
>
> Am 05.11.2013 03:03, schrieb cwillu:
>> On Mon, Nov 4, 2013 at 3:14 PM, Hendrik Friedel
>> <hendrik@friedels.name> wrote:
>>> Hello,
>>>
>>> the list was quite full with patches, so this might have been hidden.
>>> Here the complete Stack.
>>> Does this help? Is this what you needed?
>>>> [95764.899294] CPU: 1 PID: 21798 Comm: umount Tainted: GF CIO
>>>> 3.11.0-031100rc2-generic #201307211535
>>
>> Can you reproduce the problem under the released 3.11 or 3.12? An
>> -rc2 is still pretty early in the release cycle, and I wouldn't be at
>> all surprised if it was a bug added and fixed in a later rc.
>>
>
>
--
Hendrik Friedel
Auf dem Brink 12
28844 Weyhe
Mobil 0178 1874363
next prev parent reply other threads:[~2013-11-07 19:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 22:29 btrfsck errors is it save to fix? Hendrik Friedel
2013-11-02 8:12 ` cwillu
2013-11-02 8:58 ` Hendrik Friedel
2013-11-04 21:14 ` Hendrik Friedel
2013-11-05 2:03 ` cwillu
2013-11-06 6:45 ` Hendrik Friedel
2013-11-07 19:16 ` Hendrik Friedel [this message]
2013-11-08 10:09 ` Duncan
2013-11-09 8:33 ` Hendrik Friedel
2013-11-11 19:06 ` Hendrik Friedel
2013-11-11 23:58 ` Kai Krakow
2013-11-12 7:32 ` Duncan
2013-11-12 19:37 ` Kai Krakow
2013-11-13 12:20 ` Duncan
2013-11-13 12:24 ` Duncan
2013-11-16 12:32 ` Hendrik Friedel
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=527BE712.40304@friedels.name \
--to=hendrik@friedels.name \
--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 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).