public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "SCHEFFER, Philippe" <Philippe.SCHEFFER@inist.fr>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: RE : xfs_repair fails with corrupt dinode
Date: Thu, 29 Jan 2015 19:27:32 -0500	[thread overview]
Message-ID: <20150130002732.GB24547@laptop.bfoster> (raw)
In-Reply-To: <20150129234512.GF6282@dastard>

[-- Attachment #1: Type: text/plain, Size: 3674 bytes --]

On Fri, Jan 30, 2015 at 10:45:12AM +1100, Dave Chinner wrote:
> On Thu, Jan 29, 2015 at 05:56:46PM -0500, Brian Foster wrote:
> > On Thu, Jan 29, 2015 at 11:09:48PM +0100, SCHEFFER, Philippe wrote:
> > > I join info in attached files.
> > > 
> > > Chronology:
> > > Problem detected on FS.
> > 
> > Do you have a record/log of the original problem? Did the fs shutdown?
> > 
> > > FS unmounted
> > > multiple xfs_repair -P  with message in my precedent mail
> > > A try to remount FS give a kernel panic
> > 
> > I suspect a problem during log replay. Do you have a record of this
> > panic? From your comments, I take it this is now 100% reproducible.
> > 
> > There's quite a lot of noise in the repair output besides the final
> > error. Did repair ever complain about a dirty log?
> 
> Argh, off-list reply. Brian, can you attach the repair output - it's
> not in the body of your reply.
> 

Hmm, the list looks CC'd on the original. Perhaps the mail didn't make
it through. Attached again here so they should come through with you on
CC at least...

Brian

> > > Linux vp-istex-li 3.11.0-26-generic #45~precise1-Ubuntu SMP Tue Jul 15 04:02:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> > > 
> > > xfs_repair version 3.1.7
> 
> First: upgrade to 3.2.2, run repair again.
> 
> > > /dev/mapper/system-tmp /tmp ext4 rw,relatime,data=ordered 0 0
> > > /dev/mapper/system-home /home ext4 rw,relatime,data=ordered 0 0
> > > /dev/mapper/system-opt /opt ext4 rw,relatime,data=ordered 0 0
> > > /dev/mapper/system-usr /usr ext4 rw,relatime,data=ordered 0 0
> > > /dev/mapper/system-var /var ext4 rw,relatime,data=ordered 0 0
> > > /dev/mapper/data-lvol0 /applis/istex ext4 rw,relatime,data=ordered 0 0
> > > /dev/mapper/data-lvol1 /applis/getstate ext4 rw,relatime,data=ordered 0 0
> > > /dev/sde /data/brut/elsevier ext3 ro,relatime,errors=continue,barrier=1,data=ordered 0 0
> > > /dev/sdf /data/brut/rsc ext3 ro,relatime,errors=continue,barrier=1,data=ordered 0 0
> > > /dev/sdh /data/oup xfs ro,relatime,attr2,inode64,noquota 0 0
> > > /dev/sdi /data/rsc xfs rw,relatime,attr2,inode64,noquota 0 0
> > > /dev/sdn /data/nature xfs rw,relatime,attr2,inode64,noquota 0 0
> > > /dev/sdo /data/brill xfs rw,relatime,attr2,inode64,noquota 0 0
> > > /dev/sdp /data/iop xfs rw,relatime,attr2,inode64,noquota 0 0
> > > /dev/mapper/vgistex--brut-lvol00 /data/brut/wiley xfs rw,relatime,attr2,inode64,noquota 0 0
> > > /dev/mapper/vgistex--work-lvol00 /data/brut/temp xfs rw,relatime,attr2,inode64,noquota 0 0
> > > /dev/mapper/vgistex--sample-lvol0 /data/sample ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0
> > > /dev/mapper/vgistex--corpus-lvol00 /data/springer ext3 ro,relatime,errors=continue,barrier=1,data=ordered 0 0
> > > /dev/mapper/vgistex--corpus-lvol01 /data/ecco ext4 ro,relatime,data=ordered 0 0
> > > /dev/mapper/vgeebo-lvol00 /data/eebo ext3 ro,relatime,errors=continue,barrier=1,data=ordered 0 0
> > > /dev/mapper/vgistex--corpus-lvol02 /data/wiley xfs ro,relatime,attr2,inode64,noquota 0 0
> > > /dev/mapper/vgli2-lvol0 /applis/istex/corpusOutput ext4 rw,relatime,data=ordered 0 0
> > > /dev/mapper/vgli2-lvol1 /applis/istex/li2 ext4 rw,relatime,data=ordered 0 0
> > > /dev/sda1 /boot ext2 rw,relatime,errors=continue,user_xattr,acl 0 0
> > > rpc_pipefs /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
> > > nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
> 
> Which of these filesystems is the one that is problematic?
> 
> > > xfs_info : not possible, FS not mounted. Last try of mount give a Kernel panic.
> 
> It shouldn't do that. please post the stack trace and preceding
> error messages...
> 
> Cheers,
> 
> Dave.
> 
> -- 
> Dave Chinner
> david@fromorbit.com

[-- Attachment #2: xfs_info.txt.bz2 --]
[-- Type: application/x-bzip2, Size: 29561 bytes --]

[-- Attachment #3: xfs_repair_P.log.bz2 --]
[-- Type: application/x-bzip2, Size: 535670 bytes --]

[-- Attachment #4: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-01-30  0:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 15:48 xfs_repair fails with corrupt dinode SCHEFFER, Philippe
2015-01-29 17:34 ` Brian Foster
     [not found]   ` <587A9635632B174A943E53AF3B58A9082E3BE068D0@vanda>
2015-01-29 22:56     ` RE : " Brian Foster
2015-01-29 23:45       ` Dave Chinner
2015-01-30  0:27         ` Brian Foster [this message]
2015-01-29 23:15 ` Dave Chinner
     [not found]   ` <587A9635632B174A943E53AF3B58A9082E3C81A6FB@vanda>
2015-01-30  5:52     ` RE : " Dave Chinner
2015-01-30 14:37       ` RE : " SCHEFFER, Philippe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150130002732.GB24547@laptop.bfoster \
    --to=bfoster@redhat.com \
    --cc=Philippe.SCHEFFER@inist.fr \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox