On 11/28/16 10:10 AM, Will Dormann wrote: > Another possible scenario that I'm wondering whether it's plausible: > > My XFS filesystem was mildly corrupted (e.g. because of power failure or > other trouble). But not in a way that was checked/noticed/corrected > automatically on system boot, or even had a noticeable effect on the > system other than the missing file on xfsrestore? There is no explicit check on boot for xfs, so nothing would happen there. If the fs were corrupted, it likely would have been noticed by the kernel when xfsdump was traversing the filesystem. If the filesystem didn't shut down, and you didn't see anything in kernel messages, then there is likely no corruption. You could always unmount & check manually w/ xfs_repair (possibly with -n) to confirm. > The system is back up and running, seemingly-fine. But perhaps > obviously, my main concern here is to avoid this kind of scenario in the > future. e.g., is there something I'm missing in my backup routine? > Silent failures on backup/restore are not very reassuring. Can you check timestamps on the file to be sure that your assumption that it's not getting written is correct? I know cups likes to write and rewrite config files even if no changes occur, for example. -Eric > > > Thanks! > -WD > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
