| To: | Jeffrey <grndlvl@xxxxxxxxx> |
|---|---|
| Subject: | Re: xfsdump INTERRUPT issue |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 3 Jan 2013 08:48:05 +1100 |
| Cc: | stan@xxxxxxxxxxxxxxxxx, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <50D70A4B.8040904@xxxxxxxxx> |
| References: | <50D2A038.2040501@xxxxxxxxxxxxxxxxx> <CCF8A128.B0C13%jellis@xxxxxxxx> <20121221032026.GD15182@dastard> <FBB37644-0ED3-446B-BAAA-92E1389BB9DC@xxxxxxxx> <50D49899.2090901@xxxxxxxxxxxxxxxxx> <9AF752E5-941B-491F-A7DE-5D978DFFB3B0@xxxxxxxx> <50D57382.2060900@xxxxxxxxxxxxxxxxx> <50D5DB70.3020308@xxxxxxxxx> <20121222234532.GH15182@dastard> <50D70A4B.8040904@xxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Sun, Dec 23, 2012 at 08:42:35AM -0500, Jeffrey wrote: > Here's my output: > > # xfs_repair -n -r /dev/sda3 /dev/sda2 .... SO nothing apparentyl wrong with the filesytem on disk, so the corruption is occurring in memory and the oops is occurring before anything bad gets written to disk. I've tried reproducing it, but I'm not having any luck at the moment. Can you send me an ls -lR output so i can see the rough structure of the files being backed up? (Send it privately to me if you don't want everyone to see the contents of your disk....). Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] xfstests: SGI license update, Andrew Dahl |
|---|---|
| Next by Date: | hole punching performance, Bradley C. Kuszmaul |
| Previous by Thread: | Re: xfsdump INTERRUPT issue, J. Ellis |
| Next by Thread: | Re: xfsdump INTERRUPT issue, Jeffrey Ellis |
| Indexes: | [Date] [Thread] [Top] [All Lists] |