[Top] [All Lists]

Re: XFS allows expansions, but no contraction?

To: linux-xfs@xxxxxxxxxxx
Subject: Re: XFS allows expansions, but no contraction?
From: Scott McDermott <mcdermot@xxxxxxxxxxx>
Date: Fri, 27 Sep 2002 20:43:16 -0400
In-reply-to: <20020928022610.A9796@wotan.suse.de>; from ak@suse.de on Sat, Sep 28, 2002 at 02:26:10AM +0200
Mail-followup-to: linux-xfs@xxxxxxxxxxx
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>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/
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.

the inodes have to remain constant to be realistic...NFS cookies aren't
the only thing that uses them (although I can't think of anything else
that would care ;)

<Prev in Thread] Current Thread [Next in Thread>