linux-kernel - Re: BUG: XFS internal error xfs_trans

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081009230227.GL9597@disturbed>
Date:	Fri, 10 Oct 2008 10:02:27 +1100
From:	Dave Chinner <david@...morbit.com>
To:	Sean Purdy <sean-kernel@...dy.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: BUG: XFS internal error xfs_trans_cancel in 2.6.27

On Thu, Oct 09, 2008 at 11:36:10AM +0100, Sean Purdy wrote:
> Hi,
> 
> 
> Further to the discussion (and patching) of an xfs_trans_cancel
> issue in June, in kernel < 2.6.26
> 
> A similar issue came up on one disk of a 4 x 750GiB machine
> with a 2.6.24 kernel.  So I installed 2.6.27-6 and gave it another try.
> But I'm still seeing the same problem.  Remounting the drive each time
> is fine, and xfs_check shows no errors.

2.6.27-6? You mean 2.6.27-rc6?

Anyway, you need to try this patch:

http://oss.sgi.com/archives/xfs/2008-10/msg00105.html

which I posted a few days ago that fixes the latest reproducable
case of this shutdown that I know of.

If that patch doesn't fix it, what you need to do is get the
filesystem into a state where this sequence of commands can be
repeated:

# mount <dev> <mntpt>
# cd <mntpt>/some/dir/in/fs/where/error/is/occurring
# touch <somefile>
[ filesystem shuts down ]

At that point, if you provide me with an xfs_metadump image and
the exact commands to reproduce the shutdown, I will be able to
find the problem and patch it pretty quickly.

Cheers,

Dave.
-- 
Dave Chinner
david@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/