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

Results:

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

Total 18 documents matching your query.

1. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Christian Affolter <c.affolter@xxxxxxxxxxxxxxxxx>; Date: Mon, 04 Aug 2008 18:47:46 +0200; On Wed, Jul 23, 2008 at 07:40:19PM +0200, Christian Affolter wrote: Kernel-Error: Filesystem "sdc1": XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xffffffff803; /archives/xfs/2008-08/msg00062.html (12,959 bytes)
2. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 5 Aug 2008 10:19:52 +1000; Ok, what we need is the following. First, try to reproduce the problem on a small filesystem (say a few GB). Once you've reproduced the problem, unmount and remount the filesystem to get the log repl; /archives/xfs/2008-08/msg00063.html (10,439 bytes)
3. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Christian Affolter <c.affolter@xxxxxxxxxxxxxxxxx>; Date: Mon, 11 Aug 2008 14:26:30 +0200; Hi Dave On Wed, Jul 23, 2008 at 07:40:19PM +0200, Christian Affolter wrote: Kernel-Error: Filesystem "sdc1": XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xffff; /archives/xfs/2008-08/msg00170.html (11,653 bytes)
4. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 12 Aug 2008 09:52:44 +1000; You probably didn't need to do that. from the man page: By default, xfs_metadump obfuscates most file (regular file, directory and symbolic link) names and extended attribute names to allow the dumps; /archives/xfs/2008-08/msg00176.html (11,669 bytes)
5. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: xx>; Date: Mon, 04 Aug 2008 18:47:46 +0200; On Wed, Jul 23, 2008 at 07:40:19PM +0200, Christian Affolter wrote: Kernel-Error: Filesystem "sdc1": XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xffffffff803; /archives/xfs/2008-08/msg00510.html (12,959 bytes)
6. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: xx>; Date: Tue, 5 Aug 2008 10:19:52 +1000; Ok, what we need is the following. First, try to reproduce the problem on a small filesystem (say a few GB). Once you've reproduced the problem, unmount and remount the filesystem to get the log repl; /archives/xfs/2008-08/msg00511.html (10,439 bytes)
7. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: xx>; Date: Mon, 11 Aug 2008 14:26:30 +0200; Hi Dave On Wed, Jul 23, 2008 at 07:40:19PM +0200, Christian Affolter wrote: Kernel-Error: Filesystem "sdc1": XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xffff; /archives/xfs/2008-08/msg00618.html (11,653 bytes)
8. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: xx>; Date: Tue, 12 Aug 2008 09:52:44 +1000; You probably didn't need to do that. from the man page: By default, xfs_metadump obfuscates most file (regular file, directory and symbolic link) names and extended attribute names to allow the dumps; /archives/xfs/2008-08/msg00624.html (11,669 bytes)
9. Corruption of in-memory data detected - on heavy hard linking (score: 1): Author:; Date: Wed, 23 Jul 2008 19:40:19 +0200; Dear XFS users While using rsnapshot [1] on an XFS filesystem I encountered the following error, which I can reproduce using the bash command below: i=0; while (( $i <20 )); do rm -rf link-dir; cp -a; /archives/xfs/2008-07/msg00407.html (10,229 bytes)
10. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: uwsma); Date: Fri, 25 Jul 2008 01:20:51 -0400; 2.6.24 is pretty old. Did you try with a recent kernel? We had some fixes for in-core memory corruption although I don't remember one in this area.; /archives/xfs/2008-07/msg00509.html (7,910 bytes)
11. Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: xxxxxx>; Date: Wed, 23 Jul 2008 19:40:19 +0200; Dear XFS users While using rsnapshot [1] on an XFS filesystem I encountered the following error, which I can reproduce using the bash command below: i=0; while (( $i <20 )); do rm -rf link-dir; cp -a; /archives/xfs/2008-07/msg01030.html (10,229 bytes)
12. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: nald Douwsma); Date: Fri, 25 Jul 2008 01:20:51 -0400; 2.6.24 is pretty old. Did you try with a recent kernel? We had some fixes for in-core memory corruption although I don't remember one in this area.; /archives/xfs/2008-07/msg01132.html (7,910 bytes)
13. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Christian Affolter <c.affolter@xxxxxxxxxxxxxxxxx>; Date: Mon, 04 Aug 2008 18:47:46 +0200; Hi On Wed, Jul 23, 2008 at 07:40:19PM +0200, Christian Affolter wrote: Kernel-Error: Filesystem "sdc1": XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xffffffff8; /archives/xfs/2008-08/msg00958.html (13,076 bytes)
14. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 5 Aug 2008 10:19:52 +1000; Ok, what we need is the following. First, try to reproduce the problem on a small filesystem (say a few GB). Once you've reproduced the problem, unmount and remount the filesystem to get the log repl; /archives/xfs/2008-08/msg00959.html (10,597 bytes)
15. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Christian Affolter <c.affolter@xxxxxxxxxxxxxxxxx>; Date: Mon, 11 Aug 2008 14:26:30 +0200; Hi Dave On Wed, Jul 23, 2008 at 07:40:19PM +0200, Christian Affolter wrote: Kernel-Error: Filesystem "sdc1": XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xffff; /archives/xfs/2008-08/msg01066.html (12,087 bytes)
16. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 12 Aug 2008 09:52:44 +1000; You probably didn't need to do that. from the man page: By default, xfs_metadump obfuscates most file (regular file, directory and symbolic link) names and extended attribute names to allow the dumps; /archives/xfs/2008-08/msg01072.html (11,907 bytes)
17. Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Christian Affolter <christian.affolter@xxxxxxxxxxxxxxxxx>; Date: Wed, 23 Jul 2008 19:40:19 +0200; Dear XFS users While using rsnapshot [1] on an XFS filesystem I encountered the following error, which I can reproduce using the bash command below: i=0; while (( $i <20 )); do rm -rf link-dir; cp -a; /archives/xfs/2008-07/msg01653.html (10,250 bytes)
18. Re: Corruption of in-memory data detected - on heavy hard linking (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Fri, 25 Jul 2008 01:20:51 -0400; 2.6.24 is pretty old. Did you try with a recent kernel? We had some fixes for in-core memory corruption although I don't remember one in this area.; /archives/xfs/2008-07/msg01755.html (7,958 bytes)

Current List: 1 - 18
Page: [1]