[OpenAFS] volserver caused ext3 oops?

[Neulinger, Nathan]

Well, one _REAL_ good reason to journal /afscache is so it isn't the
only non-journalled fs on your machine. That makes a big difference if
you have an unclean boot. Especially with large caches.=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: Chris (Ducky) Chapin [mailto:cchapin@qualcomm.com]=20
> Sent: Wednesday, October 30, 2002 12:54 PM
> To: Derrick J Brashear
> Cc: openafs-info@openafs.org
> Subject: Re: [OpenAFS] volserver caused ext3 oops?
>=20
>=20
>=20
>=20
> On Wed, 30 Oct 2002, Derrick J Brashear wrote:
> > On Wed, 30 Oct 2002, Jack Neely wrote:
> > > Are there any known issues with using ext3 or ext2 for AFS server
> > > partitions?
> > none i know of
>=20
> The only thing we've run into when using ext3 was that=20
> multiplying the=20
> df of /usr/vice by 9/10 to determine what the cache size=20
> should be (before
> afsd is started for the first time) resulted in the partition=20
> filling up
> and OpenAFS complaining about no room left on device.
>=20
> My guess is that the journal eats a percentage of the up disk and
> that doesn't get taken into account.  Since I can't think of=20
> a good reason
> to journal cache data, I just mount /usr/vice as ext2 instead.
>=20
> --
>=20
>  Christopher 'Ducky' Chapin                        ducky@qualcomm.com
>  Unix Systems Administrator - Qualcomm, Inc.           (858) 651-5433
>  IT Host Services                                =20
>=20
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>=20