| To: | Iustin Pop <iusty@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS shrink functionality |
| From: | Ruben Porras <nahoo82@xxxxxxxxx> |
| Date: | Fri, 08 Jun 2007 10:23:53 +0200 |
| Cc: | David Chinner <dgc@xxxxxxx>, xfs@xxxxxxxxxxx, cw@xxxxxxxx |
| Dkim-signature: | a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=l+hkMqNQSlCffzVw4PM5LprHWtx4J3Qa7r5Yzg8sTKjztjvweDzUQpRCiZSqe2y3P3m0c1vsnQxJVUq0kp9+X7TYm40uLbL62uJDVH2Q2laSsJIVfJb9OGdz/I3zRDnLyQYtJ+NnGnG22MQmiKLoeOvISDBSEV0wJ9/+O7xKEoo= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=aJiW94djuLDMCsrCU+/8vzLqjVEbn3v6zcj9/PZnkzfQHQ9VKRfQcApKnfwxhm00Jf2ITUSukWLuARmM364P8VHBU1BYW7rNyFIbl0pAZT6QgBLYJ9uCDebK273/0Tt+ovOCOH8WO999Qr9m8u1VuxoJ2NbzBwfopvmln8vDRaA= |
| In-reply-to: | <20070604084154.GA8273@teal.hq.k1024.org> |
| References: | <1180715974.10796.46.camel@localhost> <20070604001632.GA86004887@sgi.com> <20070604084154.GA8273@teal.hq.k1024.org> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Am Montag, den 04.06.2007, 10:41 +0200 schrieb Iustin Pop: > Good to know. If there is at least more documentation about the > internals, I could try to find some time to work on this again. there is now a document explaining the XFS on disk format [0] and some presentations for training courses, I think none of this were available at the time you made the first try. Although they are not enough for our purpose. > My suggestion would be to start implementing these steps in reverse. 4) > is the most important as it touches the entire FS. If 4) is working > correctly, then 1) would be simpler (I think) Why do you think that 1) would be simpler after 4)? For what I understand, they are independent. 3) worries me, if walking the entire filesystem is needed, it want scale... Since I don't know yet the xfs code I would like to begin with 1), I see it independent from the other parts, and I can then learn more about the transactions, allocators, and walking through the xfs structures. As you did 4) one time, maybe you could try with this part of the problem if you find the needed time, taking David's suggestions into account. [0] http://oss.sgi.com/projects/xfs/papers/xfs_filesystem_structure.pdf Cheers -- Ruben Porras LinWorks GmbH
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE 964468 - XFS can ENOSPC in bad places, David Chinner |
|---|---|
| Next by Date: | TAKE 966004 - cleanup obtaining extent size hints from the inode, David Chinner |
| Previous by Thread: | Re: XFS shrink functionality, David Chinner |
| Next by Thread: | Re: XFS shrink functionality, Iustin Pop |
| Indexes: | [Date] [Thread] [Top] [All Lists] |