From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p65Aie0q251801 for ; Tue, 5 Jul 2011 05:44:40 -0500 Received: from firestarter.dermichi.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id DDC591E58FEB for ; Tue, 5 Jul 2011 03:44:39 -0700 (PDT) Received: from firestarter.dermichi.com (firestarter.dermichi.com [78.41.115.230]) by cuda.sgi.com with ESMTP id M6GV4oMRnddUnu0g for ; Tue, 05 Jul 2011 03:44:39 -0700 (PDT) Message-ID: <4E12EB13.50302@dermichi.com> Date: Tue, 05 Jul 2011 12:44:35 +0200 From: Michael Weissenbacher MIME-Version: 1.0 Subject: Re: xfs_bmap Cannot allocate memory References: <4E129B00.4020709@dermichi.com> <20110705103217.GC561@dastard> In-Reply-To: <20110705103217.GC561@dastard> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: xfs@oss.sgi.com Hi Dave! > > 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 > internal buffer cannot be allocated to hold all the extents to be > mapped in one call. > > Try using the "-n " option to reduce the number of > extents gathered per ioctl call and see if that makes the > issue go away. > Thanks, i've tried that: # xfs_bmap -n 3 /backup/tmp/cannot_allocate_memory.vhd /backup/tmp/cannot_allocate_memory.vhd: 0: [0..134279]: 444610560..444744839 1: [134280..134399]: hole 2: [134400..206495]: 433472688..433544783 # xfs_bmap -n 70000 /backup/tmp/cannot_allocate_memory.vhd | tail -n1 69999: [244690864..244690871]: 1173913592..1173913599 # xfs_bmap -n 75000 /backup/tmp/cannot_allocate_memory.vhd | tail -n1 74999: [253425664..253425671]: 1284986768..1284986775 # xfs_bmap -n 80000 /backup/tmp/cannot_allocate_memory.vhd | tail -n1 79999: [262287488..262289015]: hole # xfs_bmap -n 85000 /backup/tmp/cannot_allocate_memory.vhd | tail -n1 84999: [272607184..272613335]: 1497107288..1497113439 # xfs_bmap -n 90000 /backup/tmp/cannot_allocate_memory.vhd | tail -n1 xfs_bmap: xfsctl(XFS_IOC_GETBMAPX) iflags=0x0 ["/backup/tmp/cannot_allocate_memory.vhd"]: Cannot allocate memory - Seems that xfs_bmap reads at maximum the number of extents that i specified with -n - Seems that the file has even more then 85000 extents xfsprogs version is 3.1.5, compiled from source cheers, Michael _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs