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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_bmap\s+Cannot\s+allocate\s+memory\s*$/: 9 ]

Total 9 documents matching your query.

1. xfs_bmap Cannot allocate memory (score: 1): Author: Michael Weissenbacher <mw@xxxxxxxxxxxx>; Date: Tue, 05 Jul 2011 07:02:56 +0200; Hi List! I've got a file here on which i cannot use xfs_bmap to determine it's fragments. All that i know is that it must have a really great number of them. It was the result of running a smbd witho; /archives/xfs/2011-07/msg00079.html (7,153 bytes)
2. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 5 Jul 2011 20:32:17 +1000; Sounds like your memory is fragmented. IIRC, bmap tries to map all the extents in a single buffer, and that might cause problems for files with large numbers of extents. ENOMEM can occur if an intern; /archives/xfs/2011-07/msg00082.html (8,576 bytes)
3. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Tue, 05 Jul 2011 05:35:31 -0500; Googling the text above returns only 5 results, including your post today to this list. Thus I doubt your problem is the result of a bug in XFS or xfsprogs. Was the file being written to when you ran; /archives/xfs/2011-07/msg00083.html (8,108 bytes)
4. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Michael Weissenbacher <mw@xxxxxxxxxxxx>; Date: Tue, 05 Jul 2011 12:44:35 +0200; Hi Dave! Thanks, i've tried that: /backup/tmp/cannot_allocate_memory.vhd: 0: [0..134279]: 444610560..444744839 1: [134280..134399]: hole 2: [134400..206495]: 433472688..433544783 69999: [244690864..2; /archives/xfs/2011-07/msg00085.html (9,535 bytes)
5. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 5 Jul 2011 06:49:59 -0400; What version of xfsprogs do you use? xfsprogs 3.0.1 fixes a problem in the bmap command that looked pretty similar to what you see.; /archives/xfs/2011-07/msg00086.html (8,483 bytes)
6. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Michael Weissenbacher <mw@xxxxxxxxxxxx>; Date: Tue, 05 Jul 2011 13:01:02 +0200; Hi Christoph! Sorry, i forgot to mention that in my original post: xfs_bmap version 3.1.5; /archives/xfs/2011-07/msg00087.html (8,151 bytes)
7. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Michael Weissenbacher <mw@xxxxxxxxxxxx>; Date: Tue, 05 Jul 2011 13:08:51 +0200; No, the file has last been written 4 days ago Yes, i tried flushing the caches "echo 3 >/proc/sys/vm/drop_caches" which didn't change anything. I also did unmount, xfs_check (no errors reported), mou; /archives/xfs/2011-07/msg00089.html (8,680 bytes)
8. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 5 Jul 2011 21:39:29 +1000; Ah, there's a mismatch betwenteh man page and the implementation, then. The man page implies that "-n <num>" means query num extents at a time to map the entire file. It's implemented as "map the fir; /archives/xfs/2011-07/msg00090.html (10,620 bytes)
9. Re: xfs_bmap Cannot allocate memory (score: 1): Author: Michael Weissenbacher <mw@xxxxxxxxxxxx>; Date: Tue, 05 Jul 2011 15:18:52 +0200; Hi Dave! Ok, after i found out that fiemap is bleeding-edge (xfsprogs 3.1.5 doesn't support it) i compiled the latest git version of xfsprogs. "fiemap -v" doesn't bail out on this file but continues; /archives/xfs/2011-07/msg00092.html (10,367 bytes)

Current List: 1 - 9
Page: [1]