From: Dave Jones Subject: Re: [GIT PULL] ext4 updates for 3.9 Date: Wed, 27 Feb 2013 14:11:15 -0500 Message-ID: <20130227191115.GA10710@redhat.com> References: <20130227154450.GA23402@x4> <20130227170157.GA222@x4> <98C6DE45-F050-4AAD-82E2-7352F5BB0A5D@gmail.com> <20130227172256.GA236@x4> <7BFB2135-A1F0-4B6D-9962-16E75E5560F8@gmail.com> <20130227174553.GA224@x4> <20130227184912.GA19624@thunk.org> <20130227185755.GA17786@redhat.com> <20130227190419.GB19624@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: "Theodore Ts'o" , Linus Torvalds , Markus Trippelsdorf , "gnehzuil.liu" , Zheng Liu , Borislav Petkov , "linux-ext4@vger.kernel.org" , "linux-kernel@vger.kernel.org" Return-path: Content-Disposition: inline In-Reply-To: <20130227190419.GB19624@thunk.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org 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