xfs
[Top] [All Lists]

Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1

To: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 1 Nov 2010 23:52:14 +1100
Cc: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <4CCEB27E.1000605@xxxxxxxxxxxx>
References: <4CC67450.9020602@xxxxxxxxxxxx> <20101026092205.086c0d89@xxxxxxxxxxxxxx> <4CC68249.7050409@xxxxxxxxxxxx> <4CCE73C8.8070705@xxxxxxxxxxxx> <20101101122751.GL2715@dastard> <4CCEB27E.1000605@xxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
[ please don't top-post - fixed. ]

On Mon, Nov 01, 2010 at 01:28:46PM +0100, Stefan Priebe - Profihost AG wrote:
> 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?
>
> no, as Emmanuel told me i don't have todo that.

Perhaps you've been told the wrong thing.

You are getting reports of on-disk corruption being encountered. You
need to run repair to find and fix all these existing problems.
before these problems will go away. Otherwise you'll keep getting
these reports every time you read the corrupted directory....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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