[OpenAFS-devel] tracking down fileserver aborts...

[Neulinger, Nathan]

FYI, I think we were able to find the volume that this was associated
with, and running salvager against it found a lot wrong with the volume,
however, I'd like to find out why the server itself is exiting.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Neulinger, Nathan=20
> Sent: Tuesday, March 12, 2002 9:46 AM
> To: openafs-devel@openafs.org
> Subject: [OpenAFS-devel] tracking down fileserver aborts...
>=20
>=20
> I've been getting this error on a few servers. Sometimes it seems that
> the file server is aborting shortly or immediately=20
> thereafter, but other
> times not.
>=20
> Mar 12 09:13:56 afs2 fileserver[22629]: ReallyRead(): read=20
> failed device
> 1 inode 14461289103643 errno 5=20
> Mar 12 09:13:56 afs2 last message repeated 2 times
> Mar 12 09:13:57 afs2 bosserver[529]: fs:file exited on signal 6=20
> Mar 12 09:13:57 afs2 bosserver[529]: fs:vol exited on signal 15=20
> Mar 12 09:13:57 afs2 bosserver[529]: fs:salv exited on signal 13=20
>=20
> Any thoughts on tracking this down? As near as I can tell, all of the
> cases where the server is supposed to Abort() are outputting some
> diagnostic message, but not here.=20
>=20
> -- Nathan
>=20
> ------------------------------------------------------------
> Nathan Neulinger                       EMail:  nneul@umr.edu
> University of Missouri - Rolla         Phone: (573) 341-4841
> Computing Services                       Fax: (573) 341-4216
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20