Comment 5 for bug 1783757

As described above, I tested this twice (and after the first test I had repaired it with e2fsck), so at least the second time, it did not start out damaged. (And in both cases, the file systems contained working operating systems.)

I don't remember what was wrong (what e2fsck complained about), so I guess I have to test again ...