From: Mark Goodwin <markgw@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH, needs new owner] xfs_repair memory optimization
Date: Fri, 23 Jan 2009 13:09:32 +1100 [thread overview]
Message-ID: <497926DC.1030509@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
A known limitation of xfs_repair is the large amount of memory it
requires, depending on filesystem size and number of inodes, etc.
The attached patch series, originally by Barry Bnaujok, is close to
being finished but requires a new owner to do some final testing and
polishing. It applies cleanly against top-of-tree xfsprogs-3.0.0
Thanks
-- Mark
[-- Attachment #2: repair_memory_optimization.tgz --]
[-- Type: application/octet-stream, Size: 39334 bytes --]
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-01-23 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 2:09 Mark Goodwin [this message]
2009-01-24 14:23 ` [PATCH, needs new owner] xfs_repair memory optimization Christoph Hellwig
2009-01-25 0:03 ` Mark Goodwin
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=497926DC.1030509@sgi.com \
--to=markgw@sgi.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