From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
Date: Mon, 01 Nov 2010 13:28:46 +0100 [thread overview]
Message-ID: <4CCEB27E.1000605@profihost.ag> (raw)
In-Reply-To: <20101101122751.GL2715@dastard>
no, as Emmanuel told me i don't have todo that.
Stefan
Am 01.11.2010 13:27, schrieb Dave Chinner:
> On Mon, Nov 01, 2010 at 09:01:12AM +0100, Stefan Priebe - Profihost AG wrote:
>> Hi,
>>
>> i've done all you advises - updating 3ware, setting other scheduler,
>> block size, ...
>>
>> but today i got again hundrets of these messages:
>> [318343.901809] Filesystem "sdc3": XFS internal error
>> xfs_da_do_buf(2) at line 2112 of file fs/xfs/xfs_da_btree.c. Caller
>> 0xffffffff8117bdea
>> [318343.901811]
>> [318343.901813] Pid: 20299, comm: rsync Not tainted 2.6.32.22intel #1
>> [318343.901815] Call Trace:
>> [318343.901819] [<ffffffff8117bdea>] ? xfs_da_read_buf+0x24/0x29
>> [318343.901823] [<ffffffff8117bcb7>] ? xfs_da_do_buf+0x557/0x620
>> [318343.901827] [<ffffffff8117bdea>] ? xfs_da_read_buf+0x24/0x29
>> [318343.901831] [<ffffffff810538a7>] ? bit_waitqueue+0x10/0xa0
>> [318343.901834] [<ffffffff8117bdea>] ? xfs_da_read_buf+0x24/0x29
>> [318343.901839] [<ffffffff8117f43c>] ? xfs_dir2_block_lookup_int+0x45/0x197
>> [318343.901843] [<ffffffff8117f43c>] ? xfs_dir2_block_lookup_int+0x45/0x197
>> [318343.901846] [<ffffffff813751d0>] ? tcp_write_xmit+0x466/0x96c
>> [318343.901850] [<ffffffff8117f9c2>] ? xfs_dir2_block_lookup+0x18/0xb0
>> [318343.901854] [<ffffffff8117e71c>] ? xfs_dir_lookup+0xd5/0x147
>> [318343.901857] [<ffffffff811a11bd>] ? xfs_lookup+0x47/0xa3
>> [318343.901861] [<ffffffff811a90d1>] ? xfs_vn_lookup+0x3c/0x7b
>> [318343.901865] [<ffffffff810c1de7>] ? __lookup_hash+0xfa/0x11e
>> [318343.901869] [<ffffffff810c51a8>] ? do_filp_open+0x208/0x934
>> [318343.901873] [<ffffffff810c7242>] ? poll_select_copy_remaining+0xd0/0xf3
>> [318343.901877] [<ffffffff810cd62a>] ? alloc_fd+0x67/0x10b
>> [318343.901880] [<ffffffff810b8a60>] ? do_sys_open+0x55/0x103
>> [318343.901884] [<ffffffff8100ae6b>] ? system_call_fastpath+0x16/0x1b
>
> Have you run repair to fix all the existing problems after doing all
> the firmware upgrades, etc?
>
> Cheers,
>
> Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-01 12:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 6:25 Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1 Stefan Priebe - Profihost AG
2010-10-26 7:22 ` Emmanuel Florac
2010-10-26 7:24 ` Stefan Priebe - Profihost AG
2010-10-26 7:41 ` Emmanuel Florac
2010-10-26 7:53 ` Stefan Priebe - Profihost AG
2010-10-26 11:01 ` Emmanuel Florac
2010-10-26 11:03 ` Stefan Priebe - Profihost AG
2010-10-26 11:25 ` Emmanuel Florac
2010-10-26 12:09 ` Stefan Priebe - Profihost AG
2010-10-26 13:00 ` Emmanuel Florac
2010-10-26 23:23 ` Michael Monnerie
2010-10-27 3:55 ` Dave Chinner
2010-10-27 10:58 ` Michael Monnerie
2010-10-27 20:59 ` Dave Chinner
2010-10-28 9:39 ` Michael Monnerie
2010-10-27 6:04 ` Emmanuel Florac
2010-10-27 7:00 ` Stefan Priebe - Profihost AG
2010-10-27 10:06 ` Emmanuel Florac
2010-10-27 10:08 ` Stefan Priebe - Profihost AG
2010-10-27 10:12 ` Emmanuel Florac
2010-10-27 10:22 ` Stefan Priebe - Profihost AG
2010-10-27 11:14 ` Emmanuel Florac
2010-10-26 11:30 ` Larsen, Tore Høivaag
2010-10-26 11:47 ` Emmanuel Florac
2010-11-01 8:01 ` Stefan Priebe - Profihost AG
2010-11-01 10:11 ` Emmanuel Florac
2010-11-01 10:28 ` Stefan Priebe - Profihost AG
2010-11-01 12:27 ` Dave Chinner
2010-11-01 12:28 ` Stefan Priebe - Profihost AG [this message]
2010-11-01 12:52 ` Dave Chinner
2010-11-01 13:29 ` Emmanuel Florac
2010-11-01 13:48 ` Stefan Priebe - Profihost AG
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=4CCEB27E.1000605@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=david@fromorbit.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.