From: "Bearcat Şándor" <bearcatsandor@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Files seen by some apps and not others
Date: Sun, 12 Jun 2016 17:06:11 -0600 [thread overview]
Message-ID: <CAMPo9sr1v9DsaMNPDocdSASq1gp9hkbAiodJFSzDrgs4U5YdwQ@mail.gmail.com> (raw)
In-Reply-To: <loom.20160612T172707-790@post.gmane.org>
I don't think it's memory corruption as my modules test out fine, and
the problem began when i ran the btrfs check
--repair. Someone responded that they thought that the missing files
that are playable by the media player were still in memory, but they
still play after a reboot and they're not in a tmp structure anywhere.
So could it be that the metadata is not aligned with the nodes on the
disc? If so, what should i run next to address this? A balance? A
find-root with restore -t?
Would a 'btrfs rescue chunk-recover' help at this point or damage
things further?
Thanks all.
On Sun, Jun 12, 2016 at 9:47 AM, Henk Slager <eye1tm@gmail.com> wrote:
> Bearcat Şándor <bearcatsandor <at> gmail.com> writes:
>
>> Is there a fix for the bad tree block error, which seems to be the
>> root (pun intended) of all this?
>
> I think the root cause is some memory corruption. It might be known case,
> maybe someone else recognizes something.
>
> Anyhow, if you can't and won't reproduce it, best is to test
> memory/hardware, check any software that might have overwritten something in
> memory, use a recent (mainline/stable) kernel and see if it runs stable.
--
Bearcat M. Şándor
Feline Soul Systems LLC
Voice: 872.CAT.SOUL (872.228.7685)
Fax: 406.235.7070
prev parent reply other threads:[~2016-06-12 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 19:54 Files seen by some apps and not others Bearcat Şándor
2016-06-12 2:18 ` Duncan
2016-06-12 6:47 ` Bearcat Şándor
2016-06-12 15:47 ` Henk Slager
2016-06-12 23:06 ` Bearcat Şándor [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=CAMPo9sr1v9DsaMNPDocdSASq1gp9hkbAiodJFSzDrgs4U5YdwQ@mail.gmail.com \
--to=bearcatsandor@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;
as well as URLs for NNTP newsgroup(s).