Christoph, Maybe I've found an event that triggers the fault.
If I do xfs_fsr (file system optimizer program for XFS) and then xfs_check on several filesystems, I've found several times an error reported by xfs_check on this filesystem, the message is:
bad nblocks 2 for inode 1026325, counted 3 If I run xfs_repair, after informationnal messages, I get: ... Phase 3 ... .... correcting nblocks for inode 1026325 was 2 - counted 3 ...I'm not sure it is always the same inode (probably not but I'm not sure I remmebered correctly, the system is runing on a software raid1), but it is always just before a filesystem crash if I don't run xfs_repair.
With wfs_repair, I've never the crash then.I don't know if the problem has to be assigned to the filesystem or reassigned to the xfsprogs.
Regards Jean-Luc
pgpfWPAAhFaVT.pgp
Description: PGP signature
