public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Corruption of root fs during git bisect of drm system hang
Date: Thu, 11 Jul 2013 05:36:21 +0200	[thread overview]
Message-ID: <20130711033621.GB362@x4> (raw)
In-Reply-To: <20130711003122.GR3438@dastard>

On 2013.07.11 at 10:31 +1000, Dave Chinner wrote:
> On Wed, Jul 10, 2013 at 11:06:34AM +0200, Markus Trippelsdorf wrote:
> > While bisecting a system hang, caused by the drm gpu subsystem, my root fs got
> > corrupted:
> 
> I don't see any corruption being repaired....
> 
> > 
> >  # xfs_repair /dev/sdc2
> > Phase 1 - find and verify superblock...
> > Phase 2 - using internal log
> >         - zero log...
> >         - scan filesystem freespace and inode maps...
> > agi unlinked bucket 6 is 682886 in ag 3 (inode=101346182)
> > agi unlinked bucket 7 is 11335 in ag 3 (inode=100674631)
> > agi unlinked bucket 10 is 682890 in ag 3 (inode=101346186)
> > agi unlinked bucket 21 is 981 in ag 3 (inode=100664277)
> > agi unlinked bucket 23 is 5704343 in ag 3 (inode=106367639)
> > agi unlinked bucket 29 is 211421 in ag 3 (inode=100874717)
> > agi unlinked bucket 31 is 7681375 in ag 3 (inode=108344671)
> > agi unlinked bucket 34 is 3480162 in ag 3 (inode=104143458)
> > agi unlinked bucket 40 is 211432 in ag 3 (inode=100874728)
> > agi unlinked bucket 41 is 2704937 in ag 3 (inode=103368233)
> > agi unlinked bucket 45 is 594669 in ag 3 (inode=101257965)
> > agi unlinked bucket 62 is 11902 in ag 3 (inode=100675198)
> 
> That's a filesystem that has unlinked inodes on the unlinked list.
> They get cleaned up during log replay. All the other "errors" are
> related to cleaning these up....
> 
> So what is making you think there is a corruption? What's the error
> being reported when you are using the filesystem? i.e. what's the
> entire process you go through before you get to finding this
> problem?

I was loosing my KDE settings bit by bit with every reboot during the
bisection. First my window-rules disappeared, then my desktop background
changed to default, then my taskbar moved from top to the bottom, etc.
In the end I had to restore all my .files from backup. 
And please note that xfs_repair unlinked the inodes _after_ the
filesystem has been mounted and unmounted normally. 

-- 
Markus

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

  reply	other threads:[~2013-07-11  3:36 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10  9:06 Corruption of root fs during git bisect of drm system hang Markus Trippelsdorf
2013-07-11  0:31 ` Dave Chinner
2013-07-11  3:36   ` Markus Trippelsdorf [this message]
2013-07-11  3:58     ` Dave Chinner
2013-07-11  4:12       ` Stan Hoeppner
2013-07-11  9:07         ` Markus Trippelsdorf
2013-07-11 11:28           ` Markus Trippelsdorf
2013-07-11 20:24             ` Stan Hoeppner
2013-07-11 20:40               ` Markus Trippelsdorf
2013-07-11 23:01                 ` Stan Hoeppner
2013-07-12  2:38                 ` Dave Chinner
2013-07-12  2:17           ` Dave Chinner
2013-07-12  7:07             ` Markus Trippelsdorf
2013-07-13  9:05               ` Markus Trippelsdorf
2013-07-15  2:28               ` Dave Chinner
2013-07-15  6:47                 ` Markus Trippelsdorf
2013-07-19 12:22                   ` [Bisected] " Markus Trippelsdorf
2013-07-19 12:41                     ` Stefan Ring
2013-07-19 12:51                       ` Markus Trippelsdorf
2013-07-19 16:02                         ` Eric Sandeen
2013-07-19 16:32                           ` Markus Trippelsdorf
2013-07-19 19:13                             ` Ben Myers
2013-07-19 19:56                               ` Markus Trippelsdorf
2013-07-19 20:28                                 ` Markus Trippelsdorf
2013-07-19 19:23                             ` Eric Sandeen
2013-07-19 19:53                               ` Markus Trippelsdorf
2013-07-19 21:11                     ` Mark Tinguely
2013-07-20  3:18                       ` Dave Chinner
2013-07-20 17:21                         ` Mark Tinguely
2013-07-21  7:37                           ` Dave Chinner
2013-07-20  1:48                     ` Dave Chinner
2013-07-22 10:22                       ` Dave Chinner
2013-07-22 10:47                         ` Markus Trippelsdorf
2013-07-22 22:54                           ` Dave Chinner
2013-07-11  4:15       ` Markus Trippelsdorf
2013-07-11  0:37 ` Stan Hoeppner
2013-07-11  3:47   ` Markus Trippelsdorf

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=20130711033621.GB362@x4 \
    --to=markus@trippelsdorf.de \
    --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