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@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
