Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269934AbTGPAJ1 (ORCPT ); Tue, 15 Jul 2003 20:09:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269940AbTGPAJ1 (ORCPT ); Tue, 15 Jul 2003 20:09:27 -0400 Received: from rwcrmhc11.comcast.net ([204.127.198.35]:58554 "EHLO rwcrmhc11.comcast.net") by vger.kernel.org with ESMTP id S269934AbTGPAJS (ORCPT ); Tue, 15 Jul 2003 20:09:18 -0400 From: Ivan Gyurdiev Reply-To: ivg2@cornell.edu Organization: ( ) To: Jens Axboe , Bartlomiej Zolnierkiewicz Subject: 2.6.0-test1, tcq, xfs corruption Date: Tue, 15 Jul 2003 18:33:50 -0400 User-Agent: KMail/1.5.2 Cc: LKML MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307151833.50627.ivg2@cornell.edu> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2373 Lines: 56 This is to confirm corruption with the xfs filesystem on a tcq-enabled kernel with queue depth 8 (enabled by accident actually). Previously I have experienced massive fs corruption on queue depth 8 tcq kernels with reiser, described here (no replies..): http://www.ussg.iu.edu/hypermail/linux/kernel/0307.1/1307.html http://www.ussg.iu.edu/hypermail/linux/kernel/0307.1/1396.html Is there interest in more testing from me using my old reiserfs root fs? Please reply one way or the other, as I need my hard drive space back. Here's xfs oops data: 0x0: 84 24 80 00 00 00 50 51 53 e8 2e 03 00 00 83 c4 Filesystem "hda8": XFS internal error xfs_da_do_buf(2) at line 2281 of file fs/x fs/xfs_da_btree.c. Caller 0xc0203c47 Call Trace: [] xfs_da_do_buf+0x439/0x9c0 [] xfs_da_read_buf+0x57/0x60 [] xfs_da_read_buf+0x57/0x60 [] pagebuf_get+0xb9/0x140 [] xfs_da_node_lookup_int+0x7e/0x340 [] xfs_da_read_buf+0x57/0x60 [] xfs_dir2_leafn_lookup_int+0x397/0x5d0 [] xfs_dir2_leafn_lookup_int+0x397/0x5d0 [] cache_grow+0x146/0x240 [] xfs_da_node_lookup_int+0x1ee/0x340 [] xfs_dir2_node_lookup+0x3f/0xc0 [] xfs_dir2_lookup+0x138/0x150 [] xfs_ichgtime+0x105/0x107 [] xfs_setattr+0xb8/0xee0 [] xfs_dir_lookup_int+0x4c/0x130 [] xfs_lookup+0x50/0x90 [] linvfs_lookup+0x67/0xa0 [] real_lookup+0xc8/0xf0 [] do_lookup+0x96/0xb0 [] link_path_walk+0x4af/0x8e0 [] open_namei+0x83/0x410 [] filp_open+0x3e/0x70 [] sys_open+0x5b/0x90 [] syscall_call+0x7/0xb Note on filesystems: I've had massive corruption on reiser, limited corruption on xfs, and very minor corruption on ext3. I hope this is helpful. I am continuing to run an xfs system on a tcq-enabled kernel with 32 depth queue, as this seems to be fine most of the time, except for an oops/lockup when waking from standby (I've posted another bug report). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/