> -----Ursprüngliche Nachricht----- > Von: Peter Grandi [mailto:[email protected]] > Gesendet: Dienstag, 17. Juli 2012 01:28 > An: Linux fs JFS > Betreff: Re: [Jfs-discussion] Truncated files after reboot > > > I'm sorry I should have been more precise. In my case the > > files are more than a couple of days old and they are not the > > last modified on the system, > > That's dtill not precise. What does "more than a couple of days > old" mean? And what does "last modified" mean?´
This issue has some similarities to the one I was observing on multiple machines, the cause why I banned jfs from all production. The reproducer uses hard reboots, but it also occurred on minimal systems, where reboot is very fast, e.g. <2sec (missing sync?) Last modified: files corrupted, e.g. /var/log/dmesg.3.gz (a file which is created once, never touched again, just renamed and which was quite old when getting corrupted). Fsck will then complete corruption by removing the data, before that the actions to the corrupted file content are quite random, perhaps blocks are included in more than one file at the same time. The Ubuntu issue from below has some reproducer, which wrecked each jfs filesystem back then within minutes. Perhaps one could try to use it to see if it still leads to massive fs corruption, even of files not touched? https://bugs.launchpad.net/ubuntu/+source/jfsutils/+bug/754495 http://www.mail-archive.com/[email protected]/msg01682.html ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
