Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Corruption\s+of\s+in\-memory\s+data\s+detected\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Corruption\s+of\s+in\-memory\s+data\s+detected\.\s*$/: 112 ]

Total 112 documents matching your query.

1. Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Thu, 8 Sep 2005 22:18:44 +0200 (CEST); I switched from older SGI CVS kernel (2.6.12) to current SGI CVS kernel on two systems (i386 and x86_64). But after some time ( <12 hours) on both systems appeared "Corruption of in-memory data dete; /archives/xfs/2005-09/msg00061.html (8,552 bytes)
2. Re: Corruption of in-memory data detected. (score: 1): Author: evilninja <evilninja@xxxxxxx>; Date: Fri, 09 Sep 2005 20:01:01 +0200; Jan Derfinak schrieb: ...and when you switch back to 2.6.12 it does not happen again? did you run memtest86+ overnight? i don't know about the xfs cvs repos of the kernel, but perhaps you can narrow; /archives/xfs/2005-09/msg00062.html (9,807 bytes)
3. Re: Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Fri, 9 Sep 2005 21:57:50 +0200 (CEST); 2.6.12 (SGI-XFS CVS-2005-06-14_05:00_UTC with ACLs, no debug enabled) is fine. I returned back to this kernel because I had another incident on my /home partition. 2.6.13 from SGI CVS seems to be dan; /archives/xfs/2005-09/msg00063.html (10,944 bytes)
4. Re: Corruption of in-memory data detected. (score: 1): Author: Chris Croswhite <csc@xxxxxxxxxxx>; Date: Fri, 09 Sep 2005 13:14:25 -0700; This also happens on i386 (ran into the problem last evening).; /archives/xfs/2005-09/msg00064.html (9,244 bytes)
5. Re: Corruption of in-memory data detected. (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Fri, 09 Sep 2005 16:53:26 -0500; Jan Derfinak wrote: Do you realy think that memory break on two different machines just after switch to 2.6.13 kernel? But ok I will do it this night. You're right, these messages don't often indicat; /archives/xfs/2005-09/msg00065.html (9,227 bytes)
6. Re: Corruption of in-memory data detected. (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Fri, 09 Sep 2005 17:08:27 -0500; Chris Croswhite wrote: This also happens on i386 (ran into the problem last evening). One more notice: I tried to use CONFIG_KEXEC on x86_64 and kernel could not recognize XFS superblock. I didn't tr; /archives/xfs/2005-09/msg00066.html (10,121 bytes)
7. Re: Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Sat, 10 Sep 2005 00:32:12 +0200 (CEST); Kernel: XFS_VERSION_STRING "SGI-XFS CVS-2005-09-07_05:00_UTC" I have / on ext3 and all other partitions on xfs. During boot, kernel mounted / and printed "XFS: bad magic number". I extended line 211; /archives/xfs/2005-09/msg00067.html (9,857 bytes)
8. Re: Corruption of in-memory data detected. (score: 1): Author: evilninja <evilninja@xxxxxxx>; Date: Sat, 10 Sep 2005 16:49:02 +0200; Jan Derfinak schrieb: a lot things happened from 2005-06-14 to 2.6.13. did you try a stock 2.6.13 from kernel.org? if stock 2.6.13 does not crash, maybe we could look at the diff to the current 2.6.1; /archives/xfs/2005-09/msg00068.html (9,154 bytes)
9. Re: Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Sat, 10 Sep 2005 21:08:48 +0200 (CEST); Hello. kdb, some important fixes. I just downloaded vanilla 2.6.13 and it seems that for example "TAKE 941429 - Retry linux inode cacech lookup if we found a stale inode" is not there. It is simpler; /archives/xfs/2005-09/msg00069.html (9,194 bytes)
10. Re: Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Sat, 10 Sep 2005 21:10:29 +0200 (CEST); Memory is OK. Overnight memtest ended without errors. jan --; /archives/xfs/2005-09/msg00070.html (9,233 bytes)
11. Re: Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Sat, 10 Sep 2005 23:58:24 +0200 (CEST); One more notice again: I played a little with xfs_db trying to find something wrong on my FS and I found that 'frag' command doesn't work: x86_64: xfsprogs-2.6.29 Segmentation fault xfs_db: out of me; /archives/xfs/2005-09/msg00071.html (9,101 bytes)
12. Re: Corruption of in-memory data detected. (score: 1): Author: Chris Wedgwood <cw@xxxxxxxx>; Date: Sat, 10 Sep 2005 17:55:30 -0700; I've used it on multiple machines with multiple filesystems each for a long time now (basically since it first appeared).; /archives/xfs/2005-09/msg00072.html (8,928 bytes)
13. Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Thu, 8 Sep 2005 22:18:44 +0200 (CEST); I switched from older SGI CVS kernel (2.6.12) to current SGI CVS kernel on two systems (i386 and x86_64). But after some time ( <12 hours) on both systems appeared "Corruption of in-memory data dete; /archives/xfs/2005-09/msg00276.html (8,552 bytes)
14. Re: Corruption of in-memory data detected. (score: 1): Author: evilninja <evilninja@xxxxxxx>; Date: Fri, 09 Sep 2005 20:01:01 +0200; Jan Derfinak schrieb: ...and when you switch back to 2.6.12 it does not happen again? did you run memtest86+ overnight? i don't know about the xfs cvs repos of the kernel, but perhaps you can narrow; /archives/xfs/2005-09/msg00277.html (9,807 bytes)
15. Re: Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Fri, 9 Sep 2005 21:57:50 +0200 (CEST); 2.6.12 (SGI-XFS CVS-2005-06-14_05:00_UTC with ACLs, no debug enabled) is fine. I returned back to this kernel because I had another incident on my /home partition. 2.6.13 from SGI CVS seems to be dan; /archives/xfs/2005-09/msg00278.html (10,944 bytes)
16. Re: Corruption of in-memory data detected. (score: 1): Author: Chris Croswhite <csc@xxxxxxxxxxx>; Date: Fri, 09 Sep 2005 13:14:25 -0700; This also happens on i386 (ran into the problem last evening).; /archives/xfs/2005-09/msg00279.html (9,244 bytes)
17. Re: Corruption of in-memory data detected. (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Fri, 09 Sep 2005 16:53:26 -0500; Jan Derfinak wrote: Do you realy think that memory break on two different machines just after switch to 2.6.13 kernel? But ok I will do it this night. You're right, these messages don't often indicat; /archives/xfs/2005-09/msg00280.html (9,227 bytes)
18. Re: Corruption of in-memory data detected. (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Fri, 09 Sep 2005 17:08:27 -0500; Chris Croswhite wrote: This also happens on i386 (ran into the problem last evening). One more notice: I tried to use CONFIG_KEXEC on x86_64 and kernel could not recognize XFS superblock. I didn't tr; /archives/xfs/2005-09/msg00281.html (10,121 bytes)
19. Re: Corruption of in-memory data detected. (score: 1): Author: Jan Derfinak <ja@xxxxxxxxxxxx>; Date: Sat, 10 Sep 2005 00:32:12 +0200 (CEST); Kernel: XFS_VERSION_STRING "SGI-XFS CVS-2005-09-07_05:00_UTC" I have / on ext3 and all other partitions on xfs. During boot, kernel mounted / and printed "XFS: bad magic number". I extended line 211; /archives/xfs/2005-09/msg00282.html (9,857 bytes)
20. Re: Corruption of in-memory data detected. (score: 1): Author: evilninja <evilninja@xxxxxxx>; Date: Sat, 10 Sep 2005 16:49:02 +0200; Jan Derfinak schrieb: a lot things happened from 2005-06-14 to 2.6.13. did you try a stock 2.6.13 from kernel.org? if stock 2.6.13 does not crash, maybe we could look at the diff to the current 2.6.1; /archives/xfs/2005-09/msg00283.html (9,154 bytes)

Current List: 1 - 20
Page: [1] [2] [3] [4] [5] [6]