From: Ruben Porras <nahoo82@gmail.com>
To: xfs@oss.sgi.com
Cc: iusty@k1024.org, cw@f00f.org
Subject: XFS shrink functionality
Date: Fri, 01 Jun 2007 18:39:34 +0200 [thread overview]
Message-ID: <1180715974.10796.46.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
Hello,
I'm investigating the possibility to write myself the necessary code to
shrink an xfs filesystem (I'd be able to dedicate a day/week). Trying to
know if something is already done I came across the mails of a previous
intent [0], [1] (I'm cc'ing the people involved).
At a first glance the patch is a little outdated and will no more apply
(as of linux 2.16.18, which is the last customised kernel that I was
able to run under a XEN environment), because at least the function
xfs_fs_geometry is changed.
I'm really curious about what happened to this patches and why they were
discontinued. The second part never was made public, and there was also
no answer. Was there any flaw in any of the posted code or anything in
XFS that makes it especially hard to shrink [3] that discouraged the
development?
After that, the first questions that arouse are,
would there be some assistance/groove in from the developers?
How doable is it?
What are the programmers requirements from your point of view?
Thank you.
[1] http://oss.sgi.com/archives/xfs/2005-08/msg00142.html
[2] http://oss.sgi.com/archives/xfs/2005-09/msg00038.html
[3] the only limitation that I might think of is not being able to
shrink past the internal journal.
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-06-01 17:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 16:39 Ruben Porras [this message]
2007-06-04 0:16 ` XFS shrink functionality David Chinner
2007-06-04 8:41 ` Iustin Pop
2007-06-04 9:21 ` David Chinner
2007-06-05 8:00 ` Iustin Pop
2007-06-06 1:50 ` Nathan Scott
2007-06-07 8:18 ` David Chinner
2007-06-08 8:23 ` Ruben Porras
2007-06-08 10:15 ` Iustin Pop
2007-06-08 15:12 ` David Chinner
2007-06-08 16:03 ` Iustin Pop
2007-06-09 2:15 ` David Chinner
2007-06-08 19:47 ` Ruben Porras
2007-06-14 8:35 ` Ruben Porras
2007-06-14 9:14 ` David Chinner
2007-06-08 14:44 ` David Chinner
2007-06-19 22:22 ` XFS shrink (step 0) Ruben Porras
2007-06-19 23:42 ` David Chinner
2007-06-28 10:38 ` Ruben Porras
2007-06-29 6:55 ` David Chinner
2007-07-30 17:30 ` Ruben Porras
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=1180715974.10796.46.camel@localhost \
--to=nahoo82@gmail.com \
--cc=cw@f00f.org \
--cc=iusty@k1024.org \
--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