archive mirror
 help / color / mirror / Atom feed
From: C Anthony Risinger <>
To: Clemens Eisserer <>
Subject: Re: Music-files suddenly not recognized anymore, empty files - Btrfschk reports errors
Date: Sat, 12 Jun 2010 15:50:46 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Jun 12, 2010 at 3:40 PM, Clemens Eisserer <
> wrote:
> Hi,
> Recently Amarok started to reject some of music files.
> Some files seem to be simply corrupted (mplayer is still able to play
> them), other have zero length.
> Btrfsck reports:
> root 5 inode 1371 errors 400
> found 42498768896 bytes used err is 1
> total csum bytes: 41015664
> total tree bytes: 498728960
> total fs tree bytes: 406466560
> btree space waste bytes: 110792472
> file data blocks allocated: 271306133504
> =A0referenced 46886879232
> Btrfs Btrfs v0.19
> Anything I can do to repair those errors?

have you taken any snapshots?  you could pull them from there maybe.

btrfsck is not able to repair anything yet.
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
the body of a message to
More majordomo info at

  reply	other threads:[~2010-06-12 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12 20:40 Music-files suddenly not recognized anymore, empty files - Btrfschk reports errors Clemens Eisserer
2010-06-12 20:50 ` C Anthony Risinger [this message]
2010-06-12 22:10   ` Clemens Eisserer
2010-06-12 22:39 ` Chris Mason

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).