Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271196AbTHCOqd (ORCPT ); Sun, 3 Aug 2003 10:46:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271197AbTHCOqd (ORCPT ); Sun, 3 Aug 2003 10:46:33 -0400 Received: from hell.org.pl ([212.244.218.42]:14345 "HELO hell.org.pl") by vger.kernel.org with SMTP id S271196AbTHCOqa (ORCPT ); Sun, 3 Aug 2003 10:46:30 -0400 Date: Sun, 3 Aug 2003 16:51:13 +0200 From: Karol Kozimor To: linux-kernel@vger.kernel.org Subject: [2.5/2.6] buffer layer error at fs/buffer.c:2800 when unlinking Message-ID: <20030803145113.GA31715@hell.org.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4147 Lines: 113 Hi, I've recently managed to nail down the problems that have been occuring on my machine at least since 2.5.59. I use XFS as my rootfs, no other filesystems are compiled in, but I doubt the filesystem is to blame, since the problem does not appear under 2.4, despite the similar codebase. Here's the guts: upon unlinking files in /var/{run,lock/subsys} (typically during shutdown, but not only), and when doing "dd if=/dev/urandom of=/etc/random-seed count=1 bs=512" the following traces appear: #v+ buffer layer error at fs/buffer.c:2800 Call Trace: [] drop_buffers+0xb3/0xb9 [] try_to_free_buffers+0x3c/0x96 [] linvfs_release_page+0x74/0x78 [] try_to_release_page+0x5c/0x6c [] block_invalidatepage+0xe3/0xf6 [] do_invalidatepage+0x27/0x2b [] truncate_complete_page+0x87/0x89 [] truncate_inode_pages+0xcd/0x2be [] linvfs_unlink+0x5c/0x5e [] generic_delete_inode+0xc0/0xc5 [] iput+0x55/0x6f [] sys_unlink+0x86/0x135 [] syscall_call+0x7/0xb buffer layer error at fs/buffer.c:2800 Call Trace: [] drop_buffers+0xb3/0xb9 [] try_to_free_buffers+0x3c/0x96 [] linvfs_release_page+0x74/0x78 [] try_to_release_page+0x5c/0x6c [] block_invalidatepage+0xe3/0xf6 [] do_invalidatepage+0x27/0x2b [] truncate_complete_page+0x87/0x89 [] truncate_inode_pages+0xcd/0x2be [] linvfs_unlink+0x5c/0x5e [] generic_delete_inode+0xc0/0xc5 [] iput+0x55/0x6f [] sys_unlink+0x86/0x135 [] syscall_call+0x7/0xb // that's pcmcia: one trace for /var/run/cardmgr.pid, one for // /var/lock/subsys/pcmcia buffer layer error at fs/buffer.c:2800 Call Trace: [] drop_buffers+0xb3/0xb9 [] try_to_free_buffers+0x3c/0x96 [] linvfs_release_page+0x74/0x78 [] try_to_release_page+0x5c/0x6c [] block_invalidatepage+0xe3/0xf6 [] do_invalidatepage+0x27/0x2b [] truncate_complete_page+0x87/0x89 [] truncate_inode_pages+0xcd/0x2be [] padzero+0x28/0x2a [] xfs_bmap_last_offset+0xc2/0x119 [] xfs_bmap_search_extents+0x70/0x85 [] xfs_file_last_byte+0xea/0xf7 [] xfs_itruncate_start+0x9e/0xe2 [] xfs_setattr+0xdd1/0xfc2 [] linvfs_setattr+0x11d/0x1c6 [] notify_change+0x150/0x183 [] do_truncate+0x4b/0x62 [] xfs_access+0x4d/0x5b [] permission+0x46/0x48 [] may_open+0x169/0x1ba [] open_namei+0xac/0x3f3 [] filp_open+0x43/0x69 [] sys_open+0x5b/0x8b [] syscall_call+0x7/0xb // that's dd buffer layer error at fs/buffer.c:2800 Call Trace: [] drop_buffers+0xb3/0xb9 [] try_to_free_buffers+0x3c/0x96 [] linvfs_release_page+0x74/0x78 [] try_to_release_page+0x5c/0x6c [] block_invalidatepage+0xe3/0xf6 [] do_invalidatepage+0x27/0x2b [] truncate_complete_page+0x87/0x89 [] truncate_inode_pages+0xcd/0x2be [] linvfs_unlink+0x5c/0x5e [] generic_delete_inode+0xc0/0xc5 [] iput+0x55/0x6f [] sys_unlink+0x86/0x135 [] syscall_call+0x7/0xb // that's another one -- probably /var/run/sshd.pid #v- Oddly enough, those errors do not appear when I touch and remove the files manually. I can observe this behaviour on any kernel version between 2.5.59 and 2.6.0-test2. I didn't test earlier versions. The traces come from 2.6.0-test2. FYI: I never had any fs corruption whatsoever, just those annoying messages. I'll be happy to provide any additional information. Please Cc: me, as I can't handle lkml traffic. Best regards, -- Karol 'sziwan' Kozimor sziwan@hell.org.pl - 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/