[OpenAFS] AFS CopyOnWrite problem

[Neulinger, Nathan]

We had this same problem recently... also caused volumes to repeatedly
go offline. We wound up clearing the server to another and reinstalling.
One possibility we considered that it may be volumes with too many
clones - i.e. crud left over that is no longer referenced, but stil
occupying refcounts, but didn't have any opportunity to investigate in
detail.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216
=20

> -----Original Message-----
> From: openafs-info-admin@openafs.org=20
> [mailto:openafs-info-admin@openafs.org] On Behalf Of Marc Santoro
> Sent: Thursday, March 18, 2004 2:28 PM
> To: openafs-info@openafs.org
> Subject: [OpenAFS] AFS CopyOnWrite problem
>=20
> We have two OpenAFS fileservers. After a reboot, we can no=20
> longer create
> or remove files in certain directories on one of the non-replicated
> volumes on one of the servers, as well as removing or renaming these
> directories. Files in that directory can be changed (though=20
> not removed or
> renamed), and files/directories in subdirectories work as expected.
>=20
> The failed commands print "No space left on device". There is=20
> plenty of
> space left.
>=20
> Ex:
> $ touch a
> touch: cannot touch `a': No space left on device
> $ touch foo/a (where foo is a pre-existing empty directory)
> $ rm foo/a
> $ rmdir foo
> rmdir: `foo': No space left on device
>=20
> Both AFS fileservers are running 1.2.11, on Linux 2.4.25 (Debian
> packages).
>=20
> in the FileLog, we see:
>=20
> Thu Mar 18 14:06:44 2004 CopyOnWrite failed: Partition /vicepa that
> contains volume 536870918 may be out of free inodes(errno =3D 17)
>=20
> Once for each error. The filesystem has plenty of free=20
> inodes; files can
> be created in other directories.
>=20
> Both servers have been rebooted, and "salvage"d, to no avail. Salvage
> found some inode/vnode version discrepancies, but nothing else.
>=20
> Help! :)
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20
>=20