Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Not\s+enough\s+memory\s+for\s+xfs

Results:

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

Total 14 documents matching your query.

1. S (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Mon, 26 Apr 2004 15:43:29 +0200; recently, I purchased a 200GB HDD and created a single xfs partition (hdb1) on it for storage of lots of small data files. The machine runs under Debian/GNULinux (slightly outdated unstable) with ke; /archives/xfs/2004-04/msg00210.html (11,290 bytes)
2. memory for xfs_repair (score: 1): Author: Leon Woestenberg <leonw@xxxxxxxxxxx>; Date: Mon, 26 Apr 2004 23:47:28 +0200; Hello Torsten, and xfsprogs 2.6.5. The machine seems to suffer from flaky hardware (VIA chipset and 1.5GB RAM) which shows up when copying large amounts of data (several files differ afterwards). Als; /archives/xfs/2004-04/msg00211.html (8,809 bytes)
3. 6 (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Tue, 27 Apr 2004 11:35:42 +0200; Hello Leon, Yes, indeed. Attached to a more robust machine xfs_repair stopped at the same position followed by this dmesg output: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) VM: killing pr; /archives/xfs/2004-04/msg00214.html (8,311 bytes)
4. memory for xfs_repair (score: 1): Author: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>; Date: Tue, 27 Apr 2004 12:33:45 +0200; several people experienced this, as seen on lkml. (not only with xfs) Could you go for a try with 2.4.26 ? (try with the oom killer first, then, if it still not works, without the oom killer enabled; /archives/xfs/2004-04/msg00215.html (8,871 bytes)
5. memory for xfs_repair (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Tue, 27 Apr 2004 16:45:27 +0200; With oom killer enabled, I get Apr 27 16:36:31 sycorax kernel: Out of Memory: Killed process 1281 (xfs_repair). while without oom killer the kernel message is the same as above. And yes, both runs ag; /archives/xfs/2004-04/msg00216.html (9,091 bytes)
6. advice request 2.4.23 (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: 27 Apr 2004 10:56:56 -0500; xfs_repair can indeed take a lot of memory, although I don't have a good rule of thumb for how much it might take for a given filesystem. 3G does seem excessive, but you have 200G of "very small fil; /archives/xfs/2004-04/msg00218.html (10,720 bytes)
7. us of Linux on Alpha? (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Wed, 28 Apr 2004 09:37:22 +0200; I have a 160GB harddrive to rescue the remaining data. First, I'm going to add this space as swapspace, which is hopefully enough. I'll also give the latest xfsprogs a try. magicnum = 0x58465342 bloc; /archives/xfs/2004-04/msg00235.html (9,806 bytes)
8. XFS (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Mon, 26 Apr 2004 15:43:29 +0200; recently, I purchased a 200GB HDD and created a single xfs partition (hdb1) on it for storage of lots of small data files. The machine runs under Debian/GNULinux (slightly outdated unstable) with ke; /archives/xfs/2004-04/msg00474.html (11,290 bytes)
9. ing up XFS (score: 1): Author: Leon Woestenberg <leonw@xxxxxxxxxxx>; Date: Mon, 26 Apr 2004 23:47:28 +0200; Hello Torsten, and xfsprogs 2.6.5. The machine seems to suffer from flaky hardware (VIA chipset and 1.5GB RAM) which shows up when copying large amounts of data (several files differ afterwards). Als; /archives/xfs/2004-04/msg00475.html (8,809 bytes)
10. esn't work under 2.4.26 (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Tue, 27 Apr 2004 11:35:42 +0200; Hello Leon, Yes, indeed. Attached to a more robust machine xfs_repair stopped at the same position followed by this dmesg output: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) VM: killing pr; /archives/xfs/2004-04/msg00478.html (8,311 bytes)
11. up XFS (score: 1): Author: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>; Date: Tue, 27 Apr 2004 12:33:45 +0200; several people experienced this, as seen on lkml. (not only with xfs) Could you go for a try with 2.4.26 ? (try with the oom killer first, then, if it still not works, without the oom killer enabled; /archives/xfs/2004-04/msg00479.html (8,871 bytes)
12. repair (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Tue, 27 Apr 2004 16:45:27 +0200; With oom killer enabled, I get Apr 27 16:36:31 sycorax kernel: Out of Memory: Killed process 1281 (xfs_repair). while without oom killer the kernel message is the same as above. And yes, both runs ag; /archives/xfs/2004-04/msg00480.html (9,091 bytes)
13. y for xfs_repair (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: 27 Apr 2004 10:56:56 -0500; xfs_repair can indeed take a lot of memory, although I don't have a good rule of thumb for how much it might take for a given filesystem. 3G does seem excessive, but you have 200G of "very small fil; /archives/xfs/2004-04/msg00482.html (10,720 bytes)
14. res in 2.4.26 (score: 1): Author: Torsten Wolf <t.wolf@xxxxxxxx>; Date: Wed, 28 Apr 2004 09:37:22 +0200; I have a 160GB harddrive to rescue the remaining data. First, I'm going to add this space as swapspace, which is hopefully enough. I'll also give the latest xfsprogs a try. magicnum = 0x58465342 bloc; /archives/xfs/2004-04/msg00499.html (9,806 bytes)

Current List: 1 - 14
Page: [1]