From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Stan Hoeppner <stan@hardwarefreak.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:47:18 +0200 [thread overview]
Message-ID: <20130711034718.GC362@x4> (raw)
In-Reply-To: <51DDFE44.9000606@hardwarefreak.com>
On 2013.07.10 at 19:37 -0500, Stan Hoeppner wrote:
> On 7/10/2013 4:06 AM, Markus Trippelsdorf wrote:
> > While bisecting a system hang, caused by the drm gpu subsystem, my root fs got
> > corrupted:
> ...
> > My root fs lives on a small SSD:
> >
> > /dev/root on / type xfs (rw,relatime,attr2,inode64,logbsize=256k,noquota)
> > /dev/root xfs 30G 15G 16G 50% /
>
> Does your SSD honor barriers and cache flushes?
Yes, I hope so:
Enabled Supported:
...
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
But please note that the system hang mentioned above turned out to be a
locking problem. So the SSD had plenty of time to process any out-
standing commands before reboot.
--
Markus
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-07-11 3:47 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
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 [this message]
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=20130711034718.GC362@x4 \
--to=markus@trippelsdorf.de \
--cc=stan@hardwarefreak.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.