mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: XFS strangeness, xfs_db out of memory
Date: Sun, 24 Oct 2004 08:57:26 +0200	[thread overview]
Message-ID: <200410240857.31893.robin.rosenberg.lists@dewire.com> (raw)

Hi,

I was testing a tiny script on top of xfs_fsr to show fragmentation and the 
resultss of defragmentation.  As a result of fine tuning the output I ran the 
script repeatedly and suddenly got error from find (unknown error 999 if my 
memory serves me. It scrolled off the screen).

The logs show this.
Oct 24 08:06:50 xine kernel: hda: dma_timer_expiry: dma status == 0x21
Oct 24 08:07:00 xine kernel: hda: DMA timeout error
Oct 24 08:07:00 xine kernel: hda: dma timeout error: status=0xd0 { Busy }
Oct 24 08:07:00 xine kernel: 
Oct 24 08:07:00 xine kernel: hda: DMA disabled
Oct 24 08:07:00 xine kernel: ide0: reset: success

How bad is that for XFS?... The error isn't permanent it seems.

After that xfs_db -r /dev-with-home -c "frag -v" gives me an out-of-memory
error after a while, consistently.

xfs_db: out of memory

The script essentially does  this

xfs_info $dev
xfs_db -r $dev -c "frag -v"
find $mountp
xfs_fsr -v

Program versions
kernel is 2.6.8.1-12mdk (Mandrake 10.1 Community edition)
xfsdump-2.2.21-1mdk
xfsprogs-2.6.13-1mdk

xfs_repair had lots of comments after this, but went through.

-- robin

             reply	other threads:[~2004-10-24  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-24  6:57 Robin Rosenberg [this message]
2004-10-24 11:53 ` Jan Engelhardt
2004-10-24 21:05   ` Robin Rosenberg
2004-10-29  7:37 ` Nathan Scott
2004-10-31 16:58   ` Robin Rosenberg
2004-10-31 22:51     ` Nathan Scott

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=200410240857.31893.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome