xfs
[Top] [All Lists]

Re: xfs filesystem corruption with kernel 2.6.37

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfs filesystem corruption with kernel 2.6.37
From: Kamal Dasu <kdasu.kdev@xxxxxxxxx>
Date: Fri, 2 Nov 2012 21:57:27 -0400
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=045iky6n2fzNUlSKKMUf3PnJyIYMkhPqXc9Hdt6z6io=; b=pJq/oQj4TVok9GaNtmJwJFwDJjtIFMT04ojHFd+3f9EbiXR06ESvRFH1zBcDfmIhYn MxcOyl0TuWU7gjaubRi1GGsPDC/gHSXpzMDiHJJ3Txtf1PVkmW/8Kq15XncZglHLKibV agMKfVOp1LDmVH39Cq7odozt+GekHkwRx/kFoa8cOqFnS5Q8lUV6tNPBWuuEldhacdkL Ox8ND3kN9LJc0zGCmiu2K+vXnU8i09xOc23TowBKrhJKvAMbaJN1wq4XuhvitNacdQ8j nqFuUOkKp8N2mpDYIye9wbp7vj6+Ax6Y6q90tBKbCbcqSQukhPdYVFXwH/PdmWfLdR76 pi5Q==
In-reply-to: <20121102225509.GZ29378@dastard>
References: <CAC=U0a2T_J9Y6WzvWyFfbBSDy__Pr7f4gfQBie2o0VhAm2jCaQ@xxxxxxxxxxxxxx> <20121025224713.GF29378@dastard> <34630253.post@xxxxxxxxxxxxxxx> <20121102012728.GT29378@dastard> <34633803.post@xxxxxxxxxxxxxxx> <20121102225509.GZ29378@dastard>
Dave,


> 
> 0x780dbd80007f248
> 
> Once again it's corruption in the upper 32 bits of the 64 bit number.
> Those bits should be zero. Perhaps looking at all the trace events
> from recovery might give you a closer approximation of where the bad
> extent records is found....

I have been trying to use the xfs_db xfs_logprint, how ever xfs_logprint bails 
out when it finds an error. 
How do I look at trace events ?.


Kamal

<Prev in Thread] Current Thread [Next in Thread>