From: Stan Hoeppner <stan@hardwarefreak.com>
To: Shrinath M <shrinath.m@webyog.com>
Cc: Sabyasachi Ruj <sabyasachi.ruj@webyog.com>,
Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com, Vivek Goel <vivek.goel@webyog.com>,
Supratik Goswami <supratik.goswami@webyog.com>,
Ric Wheeler <rwheeler@redhat.com>
Subject: Re: XFS filesystem on EC2 instance corrupts and shuts down
Date: Thu, 14 Mar 2013 08:31:35 -0500 [thread overview]
Message-ID: <5141D137.9080509@hardwarefreak.com> (raw)
In-Reply-To: <CAOdS1hnVoMtXnOrECrU8xUyRn82UUJ=jMzX0_odnAs0GH8V-yA@mail.gmail.com>
On 3/13/2013 8:28 PM, Shrinath M wrote:
> Thanks Ben, Dave and Eric.
>
> Eric,
>>> but I am wondering if there might be more information before this which
> is not in your trimmed logs.
> No, this was the first entry every time we have it in /var/log/messages.
> dmesg also holds the same. After reboot, it simply fixes without anyone
> doing anything.
...
> - dmesg shows something like this after repairing/rebooting -
>
> [ 8.414176] SGI XFS with ACLs, security attributes, realtime, large
> block/inode numbers, no debug enabled
> [ 8.415342] SGI XFS Quota Management subsystem
> [ 8.417664] XFS (md0): Mounting Filesystem
> [ 8.771553] XFS (md0): Starting recovery (logdev: internal)
> [ 9.977325] XFS (md0): Ending recovery (logdev: internal)
The active log displayed by the dmesg command is cleared and started
fresh at each reboot, which maybe is why you don't see the IO errors.
You should find them in the previous dmesg log files.
$ ls -la /var/log/dmesg*
-rw-r--r-- 1 root adm 12K Feb 29 2012 /var/log/dmesg
-rw-r--r-- 1 root adm 12K Feb 20 2012 /var/log/dmesg.0
-rw-r--r-- 1 root adm 4.7K Aug 18 2011 /var/log/dmesg.1.gz
-rw-r--r-- 1 root adm 4.7K Aug 18 2011 /var/log/dmesg.2.gz
-rw-r--r-- 1 root adm 4.7K Jun 27 2011 /var/log/dmesg.3.gz
-rw-r--r-- 1 root adm 4.7K May 18 2011 /var/log/dmesg.4.gz
Don't let the file dates in this example throw you, here's why:
08:14:42 up 378 days, 19:44, 1 user, load average: 0.06, 0.31, 0.22
^^^^^^^^^^^
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-14 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 8:07 XFS filesystem on EC2 instance corrupts and shuts down Shrinath M
2013-03-06 12:59 ` Ric Wheeler
2013-03-06 13:03 ` Shrinath M
2013-03-06 13:08 ` Ric Wheeler
2013-03-06 13:12 ` Supratik Goswami
2013-03-06 13:15 ` Supratik Goswami
2013-03-06 14:25 ` Ric Wheeler
2013-03-13 18:07 ` Shrinath M
2013-03-13 18:24 ` Ben Myers
2013-03-13 18:56 ` Eric Sandeen
2013-03-13 19:10 ` Eric Sandeen
2013-03-13 23:42 ` Dave Chinner
2013-03-14 1:28 ` Shrinath M
2013-03-14 13:31 ` Stan Hoeppner [this message]
2013-03-14 22:02 ` Dave Chinner
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=5141D137.9080509@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=rwheeler@redhat.com \
--cc=sabyasachi.ruj@webyog.com \
--cc=sandeen@sandeen.net \
--cc=shrinath.m@webyog.com \
--cc=supratik.goswami@webyog.com \
--cc=vivek.goel@webyog.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