Date: Sat, 28 Jun 2003 09:16:15 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Gerard Samuel <gsam@trini0.org> Cc: FreeBSD Questions <questions@freebsd.org> Subject: Re: Tar Problem?? Message-ID: <20030628081615.GA11137@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <3EFD471D.2070305@trini0.org> References: <3EFD4661.8030602@trini0.org> <3EFD471D.2070305@trini0.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--vtzGhvizbBRQ85DL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Jun 28, 2003 at 03:43:25AM -0400, Gerard Samuel wrote:
> Gerard Samuel wrote:
>=20
> >Im uncompressing a file via tar, and Im getting this error ->
> >/files: create/symlink failed, no inodes free
> >tar: mpn2/themes/css/mail/mail.css: Cannot open: No such file or=20
> >directory
> >tar: Error exit delayed from previous errors
> >
> >Is this a "tar" or filesystem error??=20
The filesystem you're writing to doesn't have sufficient inodes
available to create all of the files from the tarball. Effectively
you need an inode for each file you create. Inodes are created at the
time the filesystem is generated: the newfs(8) command has an option
to set the number of bytes-per-inode: generally the defaults are fine,
but the bytes-per-inode setting should be set to no more than the
expected average size of files on the partition, and preferably rather
less than that. Running out of inodes before you run out of disk
space is embarrassing. Worse, it requires backing up the whole
partition, rebuilding the filesystem and then recovering the data from
backup in order to fix.
=20
> I forgot to include df output ->
> hivemind# df -H
> Filesystem Size Used Avail Capacity Mounted on
> /dev/da0s1a 132M 46M 76M 38% /
> /dev/da0s1g 2.7G 917M 1.6G 37% /usr
> /dev/da0s1e 103M 15M 80M 16% /var
> /dev/da0s1f 52M 387K 47M 1% /tmp
> /dev/da0s1h 320M 222M 73M 75% /files
> /dev/da0s1d 415M 77M 305M 20% /db
> /dev/ccd0c 54G 11G 39G 21% /storage
> procfs 4.1K 4.1K 0B 100% /proc
Try:
% df -iH
to add the information about inode usage to the df output. As a rule
of thumb, the %iused value should always be less than the percentage
capacity used.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--vtzGhvizbBRQ85DL
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE+/U7PdtESqEQa7a0RAiBKAJ4xCvA2mrAB1rOPcYxIpKl1Zx9GAACdGLfH
iZ18CmIau6WdmsHHfNtKwgg=
=CuLO
-----END PGP SIGNATURE-----
--vtzGhvizbBRQ85DL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030628081615.GA11137>