On Wed, Feb 27, 2013 at 02:04:19PM -0500, Theodore Ts'o wrote: > On Wed, Feb 27, 2013 at 01:57:55PM -0500, Dave Jones wrote: > > Building now. Can you confirm that nothing on-disk should be awry ? > > Or will I need a new fsck to detect what happened ? > > > > Well, it's possible that a read from data file which had blocks > located above 512GB might have gotten bogus information, or a block > allocated above 512GB might result in a write to the wrong place on > disk. > > So if you are very cautious, running fsck just to make sure things are > OK is not a bad idea. But it's likely that the directory sanity > checks would have caught things quickly, or trying run an executable > would have caused a seg fault quickly enough. If your system crashed > very quickly during the boot process, you'll probably be OK. It had been up a few hours before I hit those checks. fsck never found anything. I do have another disk (XFS formatted) with a backup from a week ago. I'll run a --dry-run rsync to see if it picks up any changes that I don't expect. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
