| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: [Bug 319] New: wishlist: allow shrinking of XFS |
| From: | Iustin Pop <iusty@xxxxxxxxx> |
| Date: | Mon, 22 Mar 2004 22:28:51 +0200 |
| Cc: | Chris Wedgwood <cw@xxxxxxxx>, bugzilla-daemon@xxxxxxxxxxx, xfs-master@xxxxxxxxxxx, brian@xxxxxxxxxxx |
| In-reply-to: | <405F465A.7020104@xxxxxxx> |
| References: | <200403210050.i2L0oseZ003869@xxxxxxxxxxx> <20040321035738.GB4143@xxxxxxxxxxxxxxxxxxxxxxx> <20040322194923.GA5404@xxxxxxxxxxxxxxxxxxxx> <405F465A.7020104@xxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.5.1+cvs20040105i |
On Mon, Mar 22, 2004 at 02:02:34PM -0600, Steve Lord wrote: > Its a little more complex than that, when you grow, you add empty space to > the fs, when you shrink, you have to move files out of the space being > removed. > > [.......] > > Not quite just the reverse of adding more free space ;-) > > Steve > Ahem, yes, uh, I imagined the space would be empty (magically). I'll make one more try, however: based on the model of xfs_fsr, couldn't the files (not the dirs) be moved in other AGs? This of course would leave the directories and maybe the inodes in the to-be-freed AGs. Just a mental exercise :) Thanks for the nice explanation. Iustin Pop |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Bug 319] New: wishlist: allow shrinking of XFS, Steve Lord |
|---|---|
| Next by Date: | Re: xfsrestore: "is a directory: discarding ino", Nathan Scott |
| Previous by Thread: | Re: [Bug 319] New: wishlist: allow shrinking of XFS, Steve Lord |
| Next by Thread: | Kernel oops in 2.4.22-1.2174.nptl_37.rhfc1.atsmp, Kjell Randa |
| Indexes: | [Date] [Thread] [Top] [All Lists] |