Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Are\s+these\s+errors\s+bad\?\s+xfs_repair\s+finding\s+errors\.\s*$/: 4 ]

Total 4 documents matching your query.

1. ng? (score: 1)
Author: Quentin Arce <qarce@xxxxxxxxx>
Date: 11 May 2002 09:21:03 -0700
ight be related to 990 which is filesystem corruption. If that happens the fs can not be read or written from and appear empty. If you then reboot it should all be there but you will need
/archives/xfs/2002-05/msg00196.html (7,409 bytes)

2. r on the 2.4.18 XFS tree? (score: 1)
Author: Quentin Arce <qarce@xxxxxxxxx>
Date: 15 May 2002 11:29:51 -0700
wrote: On Wed, 15 May 2002 07:30:09 -0400, Michael Sinz <msinz@xxxxxxxxx> wrote: I have only been able to see this behavior on my system running the kernel from the 2.4 XFS CVS tree. It i
/archives/xfs/2002-05/msg00263.html (8,836 bytes)

3. tible kernel + lock breaking? (score: 1)
Author: Quentin Arce <qarce@xxxxxxxxx>
Date: 11 May 2002 09:21:03 -0700
11:31:27AM +0200, Olaf Frączyk <olaf@xxxxxxxxxxxxx> wrote: It does not work. I think the bug is not in XFS, nor lock break. It is in the way they play together. I mean if you
/archives/xfs/2002-05/msg00834.html (7,409 bytes)

4. tree? (score: 1)
Author: Quentin Arce <qarce@xxxxxxxxx>
Date: 15 May 2002 11:29:51 -0700
, 2002-05-15 at 07:35, Keith Owens wrote: On Wed, 15 May 2002 07:30:09 -0400, Michael Sinz <msinz@xxxxxxxxx> wrote: I have only been able to see this behavior on my system run
/archives/xfs/2002-05/msg00901.html (8,836 bytes)


This search system is powered by Namazu