From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Stefan Ring <stefanrin@gmail.com>
Cc: Ben Myers <bpm@sgi.com>, Mark Tinguely <tinguely@sgi.com>,
Stan Hoeppner <stan@hardwarefreak.com>,
Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: [Bisected] Corruption of root fs during git bisect of drm system hang
Date: Fri, 19 Jul 2013 14:51:49 +0200 [thread overview]
Message-ID: <20130719125149.GB360@x4> (raw)
In-Reply-To: <CAAxjCExBi-4Qgf6-=MBzdkzBmMtu=GTURu46DoD2CzpnF2dinw@mail.gmail.com>
On 2013.07.19 at 14:41 +0200, Stefan Ring wrote:
> > I've bisected this issue to the following commit:
> >
> > commit cca9f93a52d2ead50b5da59ca83d5f469ee4be5f
> > Author: Dave Chinner <dchinner@redhat.com>
> > Date: Thu Jun 27 16:04:49 2013 +1000
> >
> > xfs: don't do IO when creating an new inode
> >
> > Reverting this commit on top of the Linus tree "solves" all problems for
> > me. IOW I no longer loose my KDE and LibreOffice config files during a
> > crash. Log recovery now works fine and xfs_repair shows no issues.
> >
> > So users of 3.11.0-rc1 beware. Only run this version if you have
> > up-to-date backups handy.
>
> What I miss in this thread is a distinction between filesystem
> corruption on the one hand and a few zeroed files on the other. The
> latter may be a nuisance, but it is expected behavior, while the
> former should never happen, period, if I'm not mistaken.
Well, it is natural that fs developers at first try to blame userspace.
Unfortunately it turned out that in this case there is filesystem
corruption. (Fortunately this normally happens only very rarely on rc1
kernels).
--
Markus
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-19 12:51 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
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 [this message]
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=20130719125149.GB360@x4 \
--to=markus@trippelsdorf.de \
--cc=bpm@sgi.com \
--cc=stan@hardwarefreak.com \
--cc=stefanrin@gmail.com \
--cc=tinguely@sgi.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