Hello,
A little while ago I noticed that a btrfsck of my home directory
produced a *lot* of the following errors:
[...]
checking fs roots
root 5 inode 3149867 errors 400, nbytes wrong
root 5 inode 3150237 errors 400, nbytes wrong
root 5 inode 3150238 errors 400, nbytes wrong
[...]
I've now piped all the inodes through "btrfs inspect-internal
inode-resolve" and made a surprising discovery: every affected inode is
a .i file in the ".hg/store/data/" directory of a Mercurial
repository. This affects multiple repositories of different projects
created and modified at different times.
As far as Mercurial is concerned, there seems to be no problem. I can
operate on the repository as always, and "hg verify" finds no issues
either.
I'm reporting this here mainly so there's a record of the
phenomenon. But if there is a btrfs test suite, maybe it'd be a good
idea to add a bunch of Mercurial repository operations to it?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
