| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS allows expansions, but no contraction? |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Sat, 28 Sep 2002 03:16:22 +0200 |
| In-reply-to: | <20020927204316.F8288@questra.com> |
| References: | <3D936DFA.5060900@emergence.com> <1033072376.17558.3.camel@stout.americas.sgi.com> <1033072540.5423.17.camel@jen.americas.sgi.com> <20020928022610.A9796@wotan.suse.de> <20020927204316.F8288@questra.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.22.1i |
On Fri, Sep 27, 2002 at 08:43:16PM -0400, Scott McDermott wrote: > Andi Kleen on Sat 28/09 02:26 +0200: > > > Probably an extension of the xfs_fsr approach would be the way to > > > go. One major issue is it is impossible to do this without changing > > > inode numbers. Some applications rely on inode numbers remaining a > > > constant. > > > > But none I know do this over umount/remount (ok except for NFS > > stateless filehandles, but that can be cured by remounting on the > > client too) > > yeah right, you have XFS for /home/ and you want to tell your hundreds > of LAN clients to remount? That is totally impractical. /home by definition never shrinks ... Also would you prefer to have no shrinking to shrinking with changed inode numbers ? -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS allows expansions, but no contraction?, Scott McDermott |
|---|---|
| Next by Date: | Suse 8.1 and XFS 1.1, Raymond |
| Previous by Thread: | Re: XFS allows expansions, but no contraction?, Scott McDermott |
| Next by Thread: | Re: XFS allows expansions, but no contraction?, Scott McDermott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |