| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: Critical xfs bug in 2.6.17.11? |
| From: | Christian Schmid <webmaster@xxxxxxxxxxxxxx> |
| Date: | Mon, 11 Sep 2006 14:29:35 +0200 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20060911005429.GK10950339@xxxxxxxxxxxxxxxxx> |
| References: | <4504151F.6050704@xxxxxxxxxxxxxx> <20060911005429.GK10950339@xxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 |
Unfortunately after this error I did a mkfs.xfs on this device, because its just a /tmp fs. David Chinner wrote: On Sun, Sep 10, 2006 at 03:37:35PM +0200, Christian Schmid wrote:Hello.Instead of a tmpfs, I use a raid 10 softraid. Unfortunately it crashed after 10 hours of extreme activities (read/block-writes with up to 250 streams/deletes)12 gb memory-test successful. 2 cpu xeon smp system. Tell me if this helps you:Sep 9 18:08:49 inode430 kernel: [87433.143498] 0x0: 58 41 47 46 00 00 00 01 00 00 00 00 00 04 34 a0 Sep 9 18:08:49 inode430 kernel: [87433.143672] Filesystem "md5": XFS internal error xfs_alloc_read_agf at line 2176 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff80314069Hmm - bad read of the AGF during allocation, which causes a shutdown due to cancelling a dirty transaction. If you run "xfs_check -n /dev/md5" and "xfs_repair -n /dev/md5" do they warn about any AGF related corruption? Cheers, Dave. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Mounting IRIX disk on Linux, Mogens Kjaer |
|---|---|
| Next by Date: | Re: Critical xfs bug in 2.6.17.11?, Christian Schmid |
| Previous by Thread: | Re: Critical xfs bug in 2.6.17.11?, David Chinner |
| Next by Thread: | xfs_repair -d doesn't work, Enrico Maria Crisostomo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |