Same failure with btrfs-progs from integration-20140421 (apart from the
line number 1156).
Can I get a bit of input on this? Is it safe to just ignore the error
for now (as I'm doing atm), ie. remount as rw to skip the orphan cleanup?
Might it even be safe to call btrfs check --repair on the partition? I'm
not keen on that failing mid-process at the same assertion and thus
breaking it over a bunch of minor files, just like it happened with my
previous btrfs partitions.
On 21.04.2014 21:13, Andreas Reis wrote:
Alright, turns out the partition does actually mount on 3.15-rc2 (error
messages remain, of course).
But systemd will fail to continue booting as /bin/mount returns "exit
status 32" and / thus ends as ro, yet can be manually remounted as rw.
Another error message I've spotted with 3.15 is
BTRFS error (device sdc5): error loading props for ino 1810424 (root
257): -5
I've now tried to mount with -o recovery and clear_cache, no effect.
--
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
