[Top] [All Lists]

Re: XFS hang during xfs_fsr run

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: XFS hang during xfs_fsr run
From: Michael Weissenbacher <mw@xxxxxxxxxxxx>
Date: Thu, 04 Mar 2010 18:14:45 +0100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20100304143018.GA417@xxxxxxxxxxxxx>
References: <4B8F871C.60802@xxxxxxxxxxxx> <20100304112018.GG14317@xxxxxxxxxxxxxxxx> <4B8FA2CD.6010904@xxxxxxxxxxxx> <20100304131511.GH14317@xxxxxxxxxxxxxxxx> <20100304134641.GA26871@xxxxxxxxxxxxx> <4B8FC1B7.3070505@xxxxxxxxxxxx> <20100304143018.GA417@xxxxxxxxxxxxx>
User-agent: Thunderbird (X11/20090817)

There's an old userspace ksymoops tool which we used before kallysyms
was around.  I don't remember the exact usage, just that it was a real

After some research on how to do a proper ksymoops i found the following information in Documentation/oops-tracing.txt: NOTE: ksymoops is useless on 2.6. Please use the Oops in its original format
(from dmesg, etc).  Ignore any references in this or other docs to "decoding
the Oops" or "running it through ksymoops". If you post an Oops from 2.6 that
has been run through ksymoops, people will just tell you to repost it.

What should i do now? I've already enabled CONFIG_KALLSYMS and rebooted.

What no-defrag flag?

# xfs_io /var/log/
xfs_io> chattr -R +f
xfs_io> lsattr
------------f- /var/log/


<Prev in Thread] Current Thread [Next in Thread>