xfs
[Top] [All Lists]

Re: XFS Kernel 2.6.27.7 oopses

To: Ralf Liebenow <ralf@xxxxxxxx>
Subject: Re: XFS Kernel 2.6.27.7 oopses
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Sun, 1 Feb 2009 11:37:44 +1100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20090130222359.GB32142@xxxxxxxx>
Mail-followup-to: Ralf Liebenow <ralf@xxxxxxxx>, xfs@xxxxxxxxxxx
References: <20090130222359.GB32142@xxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Jan 30, 2009 at 11:23:59PM +0100, Ralf Liebenow wrote:
> Hello !
> 
> I heavily use XFS for an incremental backup server (by using rsync 
> --link-dest option
> to create hardlinks to unchanged files), and therefore have about 10 million 
> files
> on my TB Harddisk. To remove old versions nightly an "rm -rf" will remove a 
> million
> hardlinks/files every night.
> 
> After a while I had regular oopses and so I updated the system to make sure 
> its
> on a current version.
> 
> It is now a SuSE 11.1 64Bit with SuSE's Kernel 2.6.27.7-9-default

What kernel did you originally see this problem on?

> <4>Call Trace:
> <4> [<ffffffff8023219a>] complete+0x38/0x4b
> <4> [<ffffffffa00f5316>] xfs_iflush+0x73/0x2ab [xfs]
> <4> [<ffffffffa010a7a2>] xfs_finish_reclaim+0x12a/0x168 [xfs]
> <4> [<ffffffffa010a871>] xfs_finish_reclaim_all+0x91/0xcb [xfs]
> <4> [<ffffffffa010925c>] xfs_syncsub+0x50/0x22b [xfs]
> <4> [<ffffffffa0118a3a>] xfs_sync_worker+0x17/0x36 [xfs]
> <4> [<ffffffffa01189d4>] xfssyncd+0x15d/0x1ac [xfs]
> <4> [<ffffffff8025434d>] kthread+0x47/0x73
> <4> [<ffffffff8020d7b9>] child_rip+0xa/0x11

That may be a use after free. I know lachlan fixed a few in this
area, but I'm not sure what release those fixeѕ ended up in....

> What do you recommend ? Has this bug already been addressed within the
> hundrets of fixes I've seen on the mailing list ? Shall I try a stock 2.6.28
> kernel ?

Try the lastest 2.6.28.x stable kernel (*not* the straight 2.6.28 release
as there's a directory traversal bug that is fixed in 2.6.28.1) and
see if the problem persists.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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