Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
I'm told that dmcrypt+XFS has never worked in the upstream kernel or in
Debian, so this is essentially an unsupported configuration. But you've
filed this bug as critical with the justification that it "causes serious
data loss". Did you lose data as a result of this bug? Could you explain
the process by which that happened? It's my impression that this
combination is so unreliable that it will oops before you really have a
chance to try to use it for storing data, so you can't really lose any data
if you can't put it there in the first place.
Based on the status as a known-buggy and unsupported config I think this bug
should be downgraded to non-RC status for etch, but I'd like to be sure
first that I understand the impact of any real-world risk of data loss.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.