Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Jan 96 19:56:32 PST
From:      Ben Jackson <bjj@sequent.com>
To:        Wilko Bulte <wilko@yedi.iaf.nl>
Cc:        roberto@keltia.freenix.fr (Ollivier Robert), mrcpu@cdsnet.net, hackers@freebsd.org
Subject:   Re: Number of superblocks on big disks. 
Message-ID:  <199601080356.TAA11113@eng4.sequent.com>
In-Reply-To: Your message of "Sun, 07 Jan 96 21:33:57 PST." <199601072033.VAA02775@yedi.iaf.nl> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <199601072033.VAA02775@yedi.iaf.nl> , you wrote:
> > Ever   used  SunOS's  newfs  to  make a    2 GB  partition   ? *That* takes
> > forever. FreeBSD's newfs is blazingly fast in comparison :-)
> 
> I think SunOS does some kind of inode randomisation. Supposedly to
> get better NFS security ??

There is an NFS attack that involves guessing the filehandles of the
files you want.  Since a fh is based on the inode number, Sun did make
this harder by randomizing the inodes.  I doubt this is really why it
takes longer, though.  A quick look at the source to FreeBSD newfs
suggests that contrary to the manual page, we default to `-i 4096'*,
wheras SunOS is defaulting to `-i 2048', which would spend twice as much
time writing inodes.

* fsize defaults to pp->p_fsize, which defaults to 1k, and density defaults
  to NFPI (4) * fsize => 4096.

--Ben



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601080356.TAA11113>