Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*unable\s+to\s+use\s+xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*unable\s+to\s+use\s+xfs_repair\s*$/: 27 ]

Total 27 documents matching your query.

1. unable to use xfs_repair (score: 1): Author: Sidik Isani <lksi@xxxxxxxxxxxxxxx>; Date: Thu, 3 Oct 2002 17:04:36 -1000; (I also sent ks; /archives/xfs/2002-10/msg00087.html (8,360 bytes)
2. Re: unable to use xfs_repair (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Fri, 04 Oct 2002 09:04:33 +0200; .0 base driver?; /archives/xfs/2002-10/msg00095.html (9,657 bytes)
3. Re: unable to use xfs_repair (score: 1): Author: Sidik Isani <lksi@xxxxxxxxxxxxxxx>; Date: Thu, 3 Oct 2002 22:41:18 -1000; t's a bit scary; /archives/xfs/2002-10/msg00097.html (10,775 bytes)
4. Re: unable to use xfs_repair (score: 1): Author: Stephen Lord <lord@xxxxxxx>; Date: 04 Oct 2002 07:06:00 -0500; l. After xfs_re; /archives/xfs/2002-10/msg00099.html (10,927 bytes)
5. Re: unable to use xfs_repair (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 04 Oct 2002 10:56:54 -0500; ds:slinx:129071; /archives/xfs/2002-10/msg00104.html (9,834 bytes)
6. Re: unable to use xfs_repair (score: 1): Author: Andi Kleen <ak@xxxxxxx>; Date: Fri, 4 Oct 2002 18:21:51 +0200; 9073a cmd/xfspr; /archives/xfs/2002-10/msg00107.html (8,643 bytes)
7. Re: unable to use xfs_repair (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 04 Oct 2002 11:44:57 -0500; s available. Th; /archives/xfs/2002-10/msg00113.html (9,034 bytes)
8. Re: unable to use xfs_repair (score: 1): Author: Andi Kleen <ak@xxxxxxx>; Date: Fri, 4 Oct 2002 18:55:04 +0200; .com/projects/x; /archives/xfs/2002-10/msg00117.html (9,431 bytes)
9. Re: unable to use xfs_repair (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 04 Oct 2002 12:00:51 -0500; continue not to; /archives/xfs/2002-10/msg00119.html (9,843 bytes)
10. panic "killing interrupt handler" and kernel BUG at sched.c:468) (score: 1): Author: III <jijo@xxxxxxxxxxx>; Date: Thu, 3 Oct 2002 17:04:36 -1000; ds very much like my problem from a few weeks ago. -- Austin Gonyou <austin@xxxxxxxxxxxxxxx> Coremetrics, Inc.; /archives/xfs/2002-10/msg00866.html (8,360 bytes)
11. nd kernel BUG at sched.c:468) (score: 1): Author: Mos <knuffie@xxxxxxxxx>; Date: Fri, 04 Oct 2002 09:04:33 +0200; ro worked fine: XFS mounting filesystem md(9,0) Ending clean XFS mount for; /archives/xfs/2002-10/msg00874.html (9,657 bytes)
12. bus error (score: 1): Author: Mos <knuffie@xxxxxxxxx>; Date: Thu, 3 Oct 2002 22:41:18 -1000; 3-10-2002 -0500, Austin Gonyou wrote: True..and we're using TIGON3 NICs (bcm5700 based stuff). I managed to crash a box with the bcm5700 driver. I am asuming you are using a 2.0 base driver?; /archives/xfs/2002-10/msg00876.html (10,775 bytes)
13. ount hangs (score: 1): Author: <lksi@xxxxxxxxxxxxxxx>; Date: 04 Oct 2002 07:06:00 -0500; pting to mount without read-only still hangs, apparently indefinitely (there's no activity on the machine.) The version of mount is 2.11u, and we're running the CVS kernel. It's a bit scary; /archives/xfs/2002-10/msg00878.html (10,927 bytes)
14. o use xfs_repair (score: 1): Author: eve Lord <lord@xxxxxxx>; Date: 04 Oct 2002 10:56:54 -0500; Hopefully this is an easy question. I would like to know how to determine the amount of usage / free space that is left in the journal. I have several filesytems that make heavy use of exte; /archives/xfs/2002-10/msg00883.html (9,834 bytes)
15. al Free Space (score: 1): Author: ndeen <sandeen@xxxxxxx>; Date: Fri, 4 Oct 2002 18:21:51 +0200; t and had a look, and we are actually as efficient as we can be in use of the memory itself. Only problem is that we allocate 4 times what we use. I fixed this in cvs. Patch against previous; /archives/xfs/2002-10/msg00886.html (8,643 bytes)
16. Space (score: 1): Author: <cattelan@xxxxxxxxxxx>; Date: 04 Oct 2002 11:44:57 -0500; remetrics, Inc.; /archives/xfs/2002-10/msg00892.html (9,034 bytes)
17. l Free Space (score: 1): Author: ndeen <sandeen@xxxxxxx>; Date: Fri, 4 Oct 2002 18:55:04 +0200; roken when we turned off large filesystem (> 2Tbytes) in the build. The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:129079a linux/f; /archives/xfs/2002-10/msg00896.html (9,431 bytes)
18. nable to use xfs_repair (score: 1): Author: arc.kaplan@xxxxxxxxxxx>; Date: 04 Oct 2002 12:00:51 -0500; d log in the code), is basically a circular on disk buffer. Metadata changes are recorded into the log, and s; /archives/xfs/2002-10/msg00898.html (9,843 bytes)
19. unable to use xfs_repair (score: 1): Author: Sidik Isani <lksi@xxxxxxxxxxxxxxx>; Date: Thu, 3 Oct 2002 17:04:36 -1000; Oct 3 16:32:10 pelmo kernel: Out of Memory: Killed process 806 (xfs_repair). Hello again - We have a bit of a problem: we have needs for very large filesystems (more than 1 TB) but no need to scale t; /archives/xfs/2002-10/msg01645.html (8,360 bytes)
20. Re: unable to use xfs_repair (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Fri, 04 Oct 2002 09:04:33 +0200; Hello again - We have a bit of a problem: we have needs for very large filesystems (more than 1 TB) but no need to scale the memory in the machines the same way ... except if you ever need to run xfs; /archives/xfs/2002-10/msg01653.html (9,691 bytes)

Current List: 1 - 20
Page: [1] [2]