Hi! > So, it seems that once the mapping is broken, it stays broken until it > is removed and recreated with cryptsetup. I have experienced something similar. It sometimes took me hours to produce the corruptions, but once I got the first warnings, every minor write operation triggered it until I rebooted (root and var filesystems were affected, so unmounting and remapping didn't work). Another thing I noticed: I was using lvm ontop of dm-crypt ontop of raid5 and some filesystems (logical volumes) would get corrupted when under heavy load, and others got corrupted when other filesystem were under heavy load. It may be coincidence but it was always the same combination: Producing heavy load on the var lv corrupted it. Producing heavy load on my data lv corrupted the root lv. All lvs were on the same volume group. Kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
