All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Weissenbacher <mw@dermichi.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_bmap Cannot allocate memory
Date: Tue, 05 Jul 2011 13:08:51 +0200	[thread overview]
Message-ID: <4E12F0C3.7080405@dermichi.com> (raw)
In-Reply-To: <4E12E8F3.4080704@hardwarefreak.com>

On Tue Jul 05 2011 12:35:31 GMT+0200 (CET), Stan Hoeppner
<stan@hardwarefreak.com> wrote:
> On 7/5/2011 12:02 AM, Michael Weissenbacher wrote:
> 
>> xfs_bmap: xfsctl(XFS_IOC_GETBMAPX) iflags=0x0
> 
> 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 xfs_bmap?
No, the file has last been written 4 days ago

> If not, did you flush caches before running xfs_bmap?  Did you try
> unmounting and remounting the filesystem?  These steps are sometimes
> needed to get actual extent usage due to extents in cache that have not
> yet been written to disk.
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), mount which didn't
change anything.

> What distro/kernel version?
Ubuntu Lucid 10.04.2 LTS with vanilla kernel 2.6.39.2

> What xfsprogs version?
Latest version 3.1.5, compiled from sources

> What filefrag version?
e2fsprogs 1.41.11-1ubuntu2.1

cheers,
Michael

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-07-05 11:08 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
2011-07-05 10:35 ` Stan Hoeppner
2011-07-05 11:08   ` Michael Weissenbacher [this message]
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=4E12F0C3.7080405@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.