On Wed, Mar 14, 2007 at 12:34:29PM +0100, Marco Berizzi wrote: > Hello everybody. > Since 2.6.19.2 + commit 7fbbb01dca7704d52ace6f45a805c98a5b0362f9
What commit is that? gitweb search tells me it's an nmi watchdog change. Doesn't seem likely to change XFS behaviour - can you post a url to the commit? > I'm experimenting these errors. > 2.6.19.1 has been worked good for more > than 30 days. With the above commit? > I have reverted back to 2.6.19.1 to see if > this problem happens again. without the above commit? > find_or_create_page+0x37/0x8e > _xfs_buf_lookup_pages+0x132/0x2ea > _xfs_buf_initialize+0xc8/0xf6 > xfs_buf_get_flags+0xf8/0x11d > xfs_buf_read_flags+0x1c/0x7f > xfs_trans_read_buf+0x16a/0x34f > xfs_itobp+0x7c/0x242 > xfs_iread+0x68/0x1d3 > xfs_iget_core+0xe7/0x687 > xfs_iget+0xd8/0x150 > xfs_dir_lookup_int+0x98/0x10e > xfs_lookup+0x5a/0x90 > xfs_vn_lookup+0x52/0x93 Curious - never seen this before - possibly a corrupted inode number in the directory has led to this. > ba 4e 8b cd > Mar 12 14:35:21 Pleiadi kernel: Filesystem "sda8": XFS internal error > xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller > 0xc01b00bd > Mar 12 14:35:21 Pleiadi kernel: [<c01affb3>] xfs_da_do_buf+0x70c/0x7b1 > Mar 12 14:35:21 Pleiadi kernel: [<c01b00bd>] xfs_da_read_buf+0x30/0x35 > Mar 12 14:35:21 Pleiadi kernel: [<c01b00bd>] xfs_da_read_buf+0x30/0x35 Hmm - these could simply be follow-on errors from the first problem - the buffer would now probably be bad or corrupted, and the directory buffer read code here is saying the buffer is bad. All the errors appear to have thesame data in the buffer (which is lacking the correct magic numbers) so i'd say they are related to the above error. Can you run xfs_repair on that filesystem and see if reports (and fixes) any problems? Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/