From: Michael Weissenbacher <mw@dermichi.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_bmap Cannot allocate memory
Date: Tue, 05 Jul 2011 15:18:52 +0200 [thread overview]
Message-ID: <4E130F3C.3050207@dermichi.com> (raw)
In-Reply-To: <20110705113929.GA21663@dastard>
Hi Dave!
>
> 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 first
> <num> extents", though.
>
> You could try this:
>
> # xfs_io -f -c "fiemap -v" <file>
>
> Because fiemap loops doing getting a small number of extents at a
> time...
>
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 to print extents
forever. I stopped it after the redirected output had already reached
90GiB and printed negative numbers. I guess it must have run into an
endless loop somewhere. xfs_bmap from the git version also throws
"Cannot allocate memory" at me.
# ./io/xfs_io -f -c "fiemap" /backup/tmp/cannot_allocate_memory.vhd >
/tmp/fiemap_output.txt
(Control-C)
# ls -lh /tmp/fiemap_output.txt
-rw-r--r-- 1 root root 90G 2011-07-05 15:06 /tmp/fiemap_output.txt
# tail -n10 /tmp/fiemap_output.txt
-1925931740: [599928..602239]: 399016..401327
-1925931739: [602240..603895]: hole
-1925931738: [603896..603903]: 2480..2487
-1925931737: [603904..606199]: hole
-1925931736: [606200..608127]: 366632..368559
-1925931735: [608128..1183]: hole
-1925931734: [1184..134279]: 444611744..444744839
-1925931733: [134280..134399]: hole
-1925931732: [134400..206495]: 433472688..433544783
-1925931731: [206496..210455]: hole
# ./io/xfs_io -f -c "bmap" /backup/tmp/cannot_allocate_memory.vhd
xfs_io: xfsctl(XFS_IOC_GETBMAPX) iflags=0x0
["/backup/tmp/cannot_allocate_memory.vhd"]: Cannot allocate memory
cheers,
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-05 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 5:02 xfs_bmap Cannot allocate memory Michael Weissenbacher
2011-07-05 10:32 ` Dave Chinner
2011-07-05 10:44 ` Michael Weissenbacher
2011-07-05 11:39 ` Dave Chinner
2011-07-05 13:18 ` Michael Weissenbacher [this message]
2011-07-05 10:35 ` Stan Hoeppner
2011-07-05 11:08 ` Michael Weissenbacher
2011-07-05 10:49 ` Christoph Hellwig
2011-07-05 11:01 ` Michael Weissenbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E130F3C.3050207@dermichi.com \
--to=mw@dermichi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox