On 5/18/12 3:57 PM, Niccolò Belli wrote: > Il 18/05/2012 19:46, Eric Sandeen ha scritto: >> the file backing it - what was that stored on? > > It was a raw image created with dd and stored on an SSD (ext4). Some > of the virtual machines were on traditional hard disks instead > (ext4). > > Only the running virtual machines got damaged, the main filesystems > are perfect. > >> What it was that did the scribbling > > Rebooting. A simple, stupid reboot after upgrading Xen. While > rebooting the system I got some kind of kernel panic and I had to use > magic sysrq keys (remount read-only, sync, reboot). Well - somehow the first sector of the xfs image got junk written into it... hard to say how that happened, but the magic number lives in the first sector of the xfs image hosted on ext4, and it was junk post-reboot. I have never seen xfs corrupt _itself_ this way. TBH I'd be as likely to blame the SSD, as anything. But you also have to have all of the data integrity bits set up properly all along the virt stack to survive a panic or power loss w/o corruption after the fact. -Eric _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
