Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_force_shutdown\s*$/: 14 ]

Total 14 documents matching your query.

1. xfs_force_shutdown (score: 1)
Author: Klaus Rein <k.rein@xxxxxxxxx>
Date: Fri, 22 Jun 2001 19:16:20 +0200
what are possible reasons for the shutdown of a xfs filesystem? Jun 21 14:28:48 probiernix4 kernel: xfs_force_shutdown(md(9,0),0x1) called from line 4069 of file xfs_bmap.c. Return address = 0xc0181
/archives/xfs/2001-06/msg00837.html (7,235 bytes)

2. Re: xfs_force_shutdown (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Fri, 22 Jun 2001 13:20:14 -0500
Forced shutdown is used when an I/O error is reported by the underlying layers. If everything else is working correctly it usually means there is a hardware problem. Once this has happened you can n
/archives/xfs/2001-06/msg00840.html (7,639 bytes)

3. Re: xfs_force_shutdown (score: 1)
Author: Klaus Rein <k.rein@xxxxxxxxx>
Date: Tue, 26 Jun 2001 19:53:51 +0200
I had already assumed that, but wanted to know for sure. The hardware is ok. Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81) We
/archives/xfs/2001-06/msg00987.html (8,733 bytes)

4. xfs_force_shutdown (score: 1)
Author: Klaus Rein <k.rein@xxxxxxxxx>
Date: Fri, 22 Jun 2001 19:16:20 +0200
what are possible reasons for the shutdown of a xfs filesystem? Jun 21 14:28:48 probiernix4 kernel: xfs_force_shutdown(md(9,0),0x1) called from line 4069 of file xfs_bmap.c. Return address = 0xc0181
/archives/xfs/2001-06/msg02007.html (7,235 bytes)

5. Re: xfs_force_shutdown (score: 1)
Author: Steve Lord <lord@xxxxxxx>
Date: Fri, 22 Jun 2001 13:20:14 -0500
Forced shutdown is used when an I/O error is reported by the underlying layers. If everything else is working correctly it usually means there is a hardware problem. Once this has happened you can n
/archives/xfs/2001-06/msg02010.html (7,639 bytes)

6. Re: xfs_force_shutdown (score: 1)
Author: Klaus Rein <k.rein@xxxxxxxxx>
Date: Tue, 26 Jun 2001 19:53:51 +0200
I had already assumed that, but wanted to know for sure. The hardware is ok. Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81) We
/archives/xfs/2001-06/msg02157.html (8,733 bytes)

7. xfs_force_shutdown (score: 1)
Author: "Hieu Le Trung" <hieult@xxxxxxxxxxxxxxxx>
Date: Mon, 12 Oct 2009 17:29:53 +0700
Hi, What may cause metadata becomes bad? I got xfs_force_shutdown with 0x2 parameter. How can I analyze the metadata dump file? Thanks, -Hieu
/archives/xfs/2009-10/msg00096.html (5,992 bytes)

8. Re: xfs_force_shutdown (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 12 Oct 2009 08:23:57 -0500
What may cause metadata becomes bad? I got xfs_force_shutdown with 0x2 parameter. Software bugs or hardware problems. If you provide the actual kernel message we can offer more info on what xfs saw a
/archives/xfs/2009-10/msg00097.html (7,858 bytes)

9. RE: xfs_force_shutdown (score: 1)
Author: "Hieu Le Trung" <hieult@xxxxxxxxxxxxxxxx>
Date: Tue, 13 Oct 2009 15:43:39 +0700
0x2 I'm not sure which one is it but the issue is hard to reproduce. I have following in the dmesg but I'm not sure it's the right one <1>I/O error in filesystem ("sda2") meta-data dev sda2 block 0xf
/archives/xfs/2009-10/msg00110.html (8,994 bytes)

10. Re: xfs_force_shutdown (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 13 Oct 2009 09:51:42 -0500
Were there IO errors from the storage before this? i.e. did some lower layer go bad. That's fine... Probably the IO errors when attempting to write to the log ... xfs_db has a manpage, but I'm not su
/archives/xfs/2009-10/msg00112.html (10,278 bytes)

11. RE: xfs_force_shutdown (score: 1)
Author: "Hieu Le Trung" <hieult@xxxxxxxxxxxxxxxx>
Date: Tue, 13 Oct 2009 22:15:14 +0700
kernel down. lower Before that is bunch of speed down request, maybe the real error has been truncated <3>ata1.00: speed down requested but no transfer mode left <3>ata1.00: exception Emask 0x0 SAct
/archives/xfs/2009-10/msg00113.html (12,002 bytes)

12. Re: xfs_force_shutdown (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 13 Oct 2009 10:31:47 -0500
Ok, so you have a storage error, and XFS is just reacting to that condition. Either turning off write caches, or using barrier support is fine: ... No; your hardware failed to write a requested log i
/archives/xfs/2009-10/msg00115.html (13,710 bytes)

13. RE: xfs_force_shutdown (score: 1)
Author: "Hieu Le Trung" <hieult@xxxxxxxxxxxxxxxx>
Date: Tue, 13 Oct 2009 22:39:39 +0700
bus http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_problem_with_the_write_c is How to check if barrier is supported in my environment? ** ** an fixing make Actually I'm implementing a filesystem whi
/archives/xfs/2009-10/msg00116.html (15,354 bytes)

14. Re: xfs_force_shutdown (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 13 Oct 2009 10:48:16 -0500
There will be a mount-time message if barrier IO fails. Yes, I think there is: <3>ata1.00: speed down requested but no transfer mode left <3>ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x10c00000 acti
/archives/xfs/2009-10/msg00117.html (9,055 bytes)


This search system is powered by Namazu