On 2016-02-01 15:27, Chris Murphy wrote:
On Mon, Feb 1, 2016 at 12:44 PM, Austin S. Hemmelgarn
<ahferro...@gmail.com> wrote:
In the process of trying to debug issues I'm having on one of my
systems with a new kernel version, I decided to do a dry run check on
the root filesystem. 'btrfs check' returned a bunch of lines like:
root 257 inode XXXXXX errors 2000, link count wrong
unresolved ref dir YYYYY index 53 namelen 3 name LOG filetype 0 errors
3, no dir item, no dir index
I got about 20 messages like this with varying values for everything
except the filetype and error counts. Based on what I can tell, these
look like orphaned inodex, but I'm not certain.
Is it safe to tell BTRFS to try and fix these errors?
Is it consistent between boots? I have a system with SSD where if I
boot with rd.break=pre-mount, and run btrfs check, I sometimes get a
long string of similar messages. But upon reboot they don't happen
anymore.
I've only checked twice, but the output is identical, so they appear to
be consistent. What seems interesting about this to me is that while
most of them are in the same directory, about 1/4 are just scattered
around the FS. None of it is anything critical though, and the system
runs just fine (or at least, it appears to, most of the issues I'm
having appear to be GPU related, and don't seem to have anything to do
with BTRFS).
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
