Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_force_shutdown\s+called\s+from\s+file\s+fs\/xfs\/xfs_trans_buf\.c\s*$/: 38 ]

Total 38 documents matching your query.

1. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Richard Freeman <freemanrich@xxxxxxxxx>
Date: Mon, 4 Aug 2008 16:55:41 +0000 (UTC)
I just started getting these on an ext3 filesystem also on gentoo, with the latest stable kernel. I suspect there is an lvm bug of some kind that is responsible. I ran an e2fsck on the filesystem and
/archives/xfs/2008-08/msg00138.html (8,565 bytes)

2. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: xx>
Date: Mon, 4 Aug 2008 16:55:41 +0000 (UTC)
I just started getting these on an ext3 filesystem also on gentoo, with the latest stable kernel. I suspect there is an lvm bug of some kind that is responsible. I ran an e2fsck on the filesystem and
/archives/xfs/2008-08/msg00586.html (8,565 bytes)

3. RE: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: "Jay Sullivan" <jpspgd@xxxxxxx>
Date: Thu, 3 Jan 2008 10:55:48 -0500
I'm still seeing a lot of the following in my dmesg. Any ideas? See below for what I have already tried (including moving data to a fresh XFS volume). Tons of these; sometimes the want= changes, but
/archives/xfs/2008-01/msg00006.html (24,836 bytes)

4. RE: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author:
Date: Thu, 3 Jan 2008 10:55:48 -0500
I'm still seeing a lot of the following in my dmesg. Any ideas? See below for what I have already tried (including moving data to a fresh XFS volume). Tons of these; sometimes the want= changes, but
/archives/xfs/2008-01/msg00245.html (24,836 bytes)

5. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Jay Sullivan <jpspgd@xxxxxxx>
Date: Thu, 20 Dec 2007 21:01:06 -0500
I'm still seeing problems. =( Most recently I have copied all of the data off of the suspect XFS volume onto another fresh XFS volume. A few days later I saw the same messages show up in dmesg. I hav
/archives/xfs/2007-12/msg00204.html (25,406 bytes)

6. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Jay Sullivan <jpspgd@xxxxxxx>
Date: Thu, 20 Dec 2007 21:01:06 -0500
I'm still seeing problems. =( Most recently I have copied all of the data off of the suspect XFS volume onto another fresh XFS volume. A few days later I saw the same messages show up in dmesg. I hav
/archives/xfs/2007-12/msg00436.html (25,406 bytes)

7. xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: "Jay Sullivan" <jpspgd@xxxxxxx>
Date: Thu, 1 Nov 2007 16:06:35 -0400
I have an XFS filesystem that has had the following happen twice in 3 months, both times with an impossibly large block number was requested. Unfortunately my logs don't go back far enough for me to
/archives/xfs/2007-11/msg00002.html (11,264 bytes)

8. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 01 Nov 2007 21:14:18 -0500
Jay Sullivan wrote: I ran xfs_repair -L on the FS and it could be mounted again, Was it not even mountable before this, or why did you use the -L flag? If the log is corrupted that points to more pro
/archives/xfs/2007-11/msg00012.html (9,395 bytes)

9. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Jay Sullivan <jpspgd@xxxxxxx>
Date: Thu, 01 Nov 2007 22:22:54 -0400
Good eye: it wasn't mountable, thus the -L flag. No recent (unplanned) power outages. The machine and the array that holds the disks are both on serious batteries/UPS and the array's cache batteries
/archives/xfs/2007-11/msg00013.html (9,628 bytes)

10. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 01 Nov 2007 21:30:17 -0500
Did you have the xfs_repair output to see what it found? You might also grab the very latest xfsprogs (2.9.4) in case it's catching more cases. I hate it when people suggest running memtest86, but I
/archives/xfs/2007-11/msg00014.html (9,936 bytes)

11. xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Jay Sullivan <jpspgd@xxxxxxx>
Date: Thu, 01 Nov 2007 22:08:09 -0400
(Sorry if this is a dupe to the list; it has been a long day.) I have an XFS filesystem that has had the following happen twice in 3 months, both times an impossibly large block number was requested.
/archives/xfs/2007-11/msg00017.html (11,285 bytes)

12. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Timothy Shimmin <tes@xxxxxxx>
Date: Fri, 02 Nov 2007 15:37:45 +1100
Eric Sandeen wrote: Jay Sullivan wrote: I ran xfs_repair -L on the FS and it could be mounted again, Was it not even mountable before this, or why did you use the -L flag? If the log is corrupted tha
/archives/xfs/2007-11/msg00018.html (10,397 bytes)

13. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Fri, 2 Nov 2007 16:18:34 +1100
.... Sure sign of a corrupted btree. <shrug> What was the problem that xfs_repair fixed? BTW, why did you run xfs_repair -L? Also, when it happens next, what does xfs_check tell you is broken? Cheers
/archives/xfs/2007-11/msg00019.html (9,462 bytes)

14. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Ralf Gross <Ralf-Lists@xxxxxxxxxxxx>
Date: Fri, 2 Nov 2007 10:07:40 +0100
Eric Sandeen schrieb: I use areca controllers with xfs, but had no problems yet. Can you explain what bugs might hit me? Ralf
/archives/xfs/2007-11/msg00020.html (9,563 bytes)

15. RE: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: "Jay Sullivan" <jpspgd@xxxxxxx>
Date: Fri, 2 Nov 2007 10:00:23 -0400
I lost the xfs_repair output on an xterm with only four lines of scrollback... I'll definitely be more careful to preserve more 'evidence' next time. =( "Pics or it didn't happen", right? I just upgr
/archives/xfs/2007-11/msg00021.html (11,021 bytes)

16. RE: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: "Jay Sullivan" <jpspgd@xxxxxxx>
Date: Fri, 2 Nov 2007 10:49:16 -0400
What can I say about Murphy and his silly laws? I just had a drive fail on my array. I wonder if this is the root of my problems... Yay parity. ~Jay I lost the xfs_repair output on an xterm with only
/archives/xfs/2007-11/msg00022.html (11,554 bytes)

17. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 02 Nov 2007 11:10:32 -0500
maybe none, it was just a wild guess. :) I've seen a bug on ext3, volumes > 2T corrupted, on an areca controller. Due to the 2T threshold, it seems more like a lower layer IO issue (2^32 x 512) than
/archives/xfs/2007-11/msg00023.html (10,335 bytes)

18. RE: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author:
Date: Wed, 14 Nov 2007 10:05:52 -0500
Of course this had to happen one more time before my scheduled maintenance window... Anyways, here's all of the good stuff I collected. Can anyone make sense of it? Oh, and I upgraded to xfsprogs 2.9
/archives/xfs/2007-11/msg00146.html (20,247 bytes)

19. Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author:
Date: Wed, 14 Nov 2007 21:26:13 -0600
Forgot to ask, are you running w/ 4k stacks? And/or, do you have stack usage debugging enabled? That's quite a backtrace you've got there... just a shot in the dark. -Eric
/archives/xfs/2007-11/msg00155.html (9,533 bytes)

20. xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c (score: 1)
Author:
Date: Thu, 1 Nov 2007 16:06:35 -0400
I have an XFS filesystem that has had the following happen twice in 3 months, both times with an impossibly large block number was requested. Unfortunately my logs don't go back far enough for me to
/archives/xfs/2007-11/msg00318.html (11,264 bytes)


This search system is powered by Namazu