I could reproduce the issue by adding a single "sync". It seems the umount in original script flushes data to loopdevice. When the caches are already flushed you will be able to reproduce the dataloss!
Btw..fsck seems unable to detect the broken filesystem!? PS: I changed from mdadm to normal mounting the loopback device ** Attachment added: "modified script" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+attachment/4238892/+files/repro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381968 Title: Fstrim destroys data on loopback device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381968/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
