Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Corrupt file in subvolume
Date: Mon, 10 Oct 2011 13:55:12 +0200	[thread overview]
Message-ID: <8j2bm8-ob9.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 20111010103723.GE17912@twin.jikos.cz

David Sterba wrote:

>> Then I could mount the /home subvolume.
>>
>> I also found the corrupted file
>>? -????????? ? ?   ?        ?            ? 13.4.4.40.js
> 
> Chromium cache? Somebody recently reported a problem there. I wonder
> what this browser does to the filesystem ... :)

If you meant me by "someone": No, my problem was not related to chromium 
usage - the problems only raised there because of a previous "cp --reflink" 
issue while I continued browsing. ;-)

So it is pure coincidence because browser caches are a probable destination 
for write access while my system came to a complete halt due to a browsing-
unrelated file operation (cp --reflink).

Regards,
Kai


      parent reply	other threads:[~2011-10-10 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10  2:14 Corrupt file in subvolume dima
2011-10-10 10:37 ` David Sterba
2011-10-10 11:03   ` dima
2011-10-10 11:29     ` David Sterba
2011-10-10 12:20       ` dima
2011-10-11 13:30         ` dima
2011-10-10 11:55   ` Kai Krakow [this message]

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=8j2bm8-ob9.ln1@hurikhan.ath.cx \
    --to=hurikhan77+btrfs@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