Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Daniel Miranda <danielkza2@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: Apparent metadata corruption (file that simultaneously does/does not exist) on kernel 3.17.3
Date: Tue, 25 Nov 2014 13:10:26 +0800	[thread overview]
Message-ID: <54740F42.2040301@cn.fujitsu.com> (raw)
In-Reply-To: <CAPRQymMYBhy0mxG1qTxqt2OGezm3qnq+rAZOLAk1TpkOoixNWw@mail.gmail.com>

Hi,

What's the btrfsck output? Without --repair option.

Also, if it is OK for you, would you please dump the btrfs with 
'btrfs-image' command?
'-c 9' option is highly recommended considering the size of it.
This will helps a lot for developers to test the btrfsck repair function.

Thanks,
Qu

-------- Original Message --------
Subject: Apparent metadata corruption (file that simultaneously 
does/does not exist) on kernel 3.17.3
From: Daniel Miranda <danielkza2@gmail.com>
To: <linux-btrfs@vger.kernel.org>
Date: 2014年11月25日 13:04
> Hello,
>
> After I had some brief stability issues with my computer, it seems
> some form of metadata corruption took place in my BTRFS filesystem,
> and now a particular file seems to exist, but I cannot access any
> details on it or delete it.
>
> If I try to `ls` in the directory it is in, that's what I get:
>
> ls: cannot access string.h: No such file or directory
> total 0
> drwxr-xr-x. 1 danielkza mock 16 Nov 21 14:18 ./
> drwxr-xr-x. 1 danielkza mock  6 Nov 21 14:18 ../
> -?????????? ? ?         ?     ?            ? string.h
>
> If I try to delete it I get:
>
> rm: cannot remove ‘string.h’: No such file or directory
>
> I'm using kernel 3.17.3 from Fedora 21. I got no messages on dmesg or
> anything of the sort. I know the btrfs fsck situation is complicated,
> but is there any utility I should use to try and repair this? Losing
> this file is not a problem, it's just one header from the kernel I was
> building.
>
> Regards,
> Daniel Miranda
> --
> 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


  reply	other threads:[~2014-11-25  5:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  5:04 Apparent metadata corruption (file that simultaneously does/does not exist) on kernel 3.17.3 Daniel Miranda
2014-11-25  5:10 ` Qu Wenruo [this message]
2014-11-25  5:14   ` Daniel Miranda
2014-11-25  5:20     ` Qu Wenruo
2014-11-25  7:20       ` Daniel Miranda
2014-11-25  7:26         ` Qu Wenruo
2014-11-25  7:42           ` Daniel Miranda
2014-11-26  2:41             ` Qu Wenruo
2014-11-26  3:07               ` Daniel Miranda
2014-12-03 12:50                 ` Daniel Miranda

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=54740F42.2040301@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=danielkza2@gmail.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