Ok, I'll skip dmesg and add xfs_info. And I'll make sure to post everything
Thanks again :)
On Dec 2, 2012, at 4:10 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> On Sat, Dec 01, 2012 at 11:03:57AM -0500, J. Ellis wrote:
>> I'm trying to prepare a question regarding an xfsdump INTERRUPT error I'm
>> getting, and I'm trying to follow the guidelines for reporting such issues
>> But these last two instructions I'm having a problem finding the information
>> on how to generate:
>> xfs_info output on the filesystem in question (I tried xfs_info /dev/sdc,
>> but it keeps saying for each drive that it's not a mounted xfs system IIRC)
> $ man xfs_info
> xfs_info [ -t mtab ] mount-point
>> dmesg output showing all error messages and stack traces
> Run the dmesg command....
>> Then you need to describe your workload that is causing the problem, and a
>> demonstration of the bad behavior that is occurring. If it is a performance
>> problem, then 30s - 1 minute samples of:
>> 1. iostat -x -d -m 5
>> 2. vmstat 5
>> Do I run this simultaneously while xfstools are working? I'm also not sure
>> what's meant by describe your workload. Can someone step me through this?
> Do you have a performance problem? I don't think you have - your problem is
> that xfsdump is failing for some reason - so this information is
> As to your workload, your problem is xfsdump is failing for some
> reason. Hence we need to know roughly what xfsdump is running on.
> i.e. describe the directory structure/filesystem contents being
> backed up....
> BTW, don't expect responses to questions in a hour late on friday
> night/weekends - if you are lucky someone will be in front of their
> computer over a weekend, sometimes you are not so lucky...
> Dave Chinner
> xfs mailing list