On Wed, Apr 1, 2015 at 11:26 AM, Martin Langhoff
<martin.langhoff@xxxxxxxxx> wrote:
> On Wed, Apr 1, 2015 at 1:03 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
>> mount /dev/sda6 /mnt
>> btrfs inspect-internal inode-resolve 39841 /mnt
>
> on the booted system...
> # uname -a
> Linux tp-martin.remote-learner.net 3.18.9-200.fc21.x86_64 #1 SMP Mon
> Mar 9 15:10:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> # btrfs inspect-internal inode-resolve 39841 /
> //etc/shadow-
> # diff -u /etc/shadow{,-}
> --- /etc/shadow 2015-03-04 02:26:59.478255332 -0500
> +++ /etc/shadow- 2015-03-04 02:26:59.000000000 -0500
> @@ -42,4 +42,3 @@
> systemd-timesync:!!:16498::::::
> systemd-network:!!:16498::::::
> systemd-resolve:!!:16498::::::
> -systemd-bus-proxy:!!:16498::::::
>
> Bizarre.
When I had this same btrfs check error, it was the exact inode number
and same /etc/shadow file. I didn't diff the two shadow files, but I
the the cp mv rm routine, and then the system booted. Goofy cakes.
It's almost like an April Fools joke.
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
