From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id oAGLqZpk123849 for ; Tue, 16 Nov 2010 15:52:35 -0600 Received: from mail.sandeen.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 33B2413C4C01 for ; Tue, 16 Nov 2010 13:54:07 -0800 (PST) Received: from mail.sandeen.net (64-131-28-21.usfamily.net [64.131.28.21]) by cuda.sgi.com with ESMTP id 2KlY9SrlfqFCzWDS for ; Tue, 16 Nov 2010 13:54:07 -0800 (PST) Message-ID: <4CE2FD7E.1040901@sandeen.net> Date: Tue, 16 Nov 2010 15:54:06 -0600 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: XFS: I/O Error Detected / 2.6.27.39 References: <4CE282DB.8060200@open-e.com> In-Reply-To: <4CE282DB.8060200@open-e.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Piotr Kandziora Cc: Artur Piechocki , lukasz.wittig@open-e.com, Janusz Bak , xfs@oss.sgi.com On 11/16/10 7:10 AM, Piotr Kandziora wrote: > Hi, > > Our environment is following: > - we have 24GB RAM, > - we are using 3ware controller (and it does not report any errors), > - we have one big logical volume (20TB) exported via NFS with large amount of small files (about 150k), > - we are doing periodically backup of this logical volume using rsync to another server. > - we have kernel 2.6.27.39, > > Unfortunately our system is freezing unexpectedly without reason. We started investigating this problem and noticed that cache memory is slowly increasing. > > We tried to dump this cache memory using: > /bin/echo "3" > /proc/sys/vm/drop_caches > > In a result, cache was dumped, but in logs we noticed a lot of errors with XFS: > > [kern.warning] kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on dm-16. Returning error. so this got EINVAL: #define EINVAL 22 /* Invalid argument */ > [kern.notice] kernel: xfs_inactive:\011xfs_ifree() returned an error = 22 on dm-16 > [kern.notice] kernel: xfs_force_shutdown(dm-16,0x1) called from line 1406 of file fs/xfs/xfs_vnodeops.c. Return address = 0x > [kern.alert] kernel: Filesystem \"dm-16\": I/O Error Detected. Shutting down filesystem: dm-16 which shut down the filesystem: > [kern.alert] kernel: Please umount the filesystem, and rectify the problem(s) leading to IO errors after that: #define EIO 5 /* I/O error */ > [kern.warning] kernel: xfs_imap_to_bp: xfs_trans_read_buf()returned an error 5 on dm-16. Returning error. > [kern.warning] kernel: xfs_imap_to_bp: xfs_trans_read_buf()returned an error 5 on dm-16. Returning error. > [kern.warning] kernel: xfs_imap_to_bp: xfs_trans_read_buf()returned an error 5 on dm-16. Returning error. > > We are wondering if this is problem connected to hardware or rather this is XFS problem (if yes, was it fixed?). I'd probably start with xfs_repair (with -n if you want a dry run) and see if it finds any metadata corruption, first. -Eric > Best regards > Piotr K > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs