filesystem shrinks after using xfs_repair

[Michael Monnerie]

On Freitag, 30. Juli 2010 Christoph Hellwig wrote:
> On Fri, Jul 30, 2010 at 12:23:08PM +0200, Michael Monnerie wrote:
> > On Freitag, 30. Juli 2010 Christoph Hellwig wrote:
> > > Recent enough kernel work fine with filesystems that inode64 was
> > > used on even if it's not specified anymore.
> >
> >  
> > Really? Since when exactly? That would be a nice feature. If we
> > can  define it clearly, I could put that on the FAQ.
> 
> Linux 2.6.35 will be the first kernel with the bugfixes for this to
> work.

Hihi, *rofl*. That's what developers mean by "recent enough kernel": It 
will be "in the next release to come". :-)

> > But how does it truncate the numbers >int32 and avoid collisions?
> 
> It doesn't.  Existing inodes won't nessecarily fit into 32-bits, but
> no new inodes above it will be allocated.

OK, sounds simple. I wrote two new FAQ entries:

http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_inode64_mount_option_for.3F

Could "all who know better than me" please verify if the information is 
correct?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://oss.sgi.com/pipermail/xfs/attachments/20100609/f2bb0570/attachment.sig>