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.
-- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Chris (Ducky) Chapin [mailto:cchapin@;qualcomm.com] > Sent: Wednesday, October 30, 2002 12:54 PM > To: Derrick J Brashear > Cc: [EMAIL PROTECTED] > Subject: Re: [OpenAFS] volserver caused ext3 oops? > > > > > 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 > > The only thing we've run into when using ext3 was that > multiplying the > df of /usr/vice by 9/10 to determine what the cache size > should be (before > afsd is started for the first time) resulted in the partition > filling up > and OpenAFS complaining about no room left on device. > > 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 > a good reason > to journal cache data, I just mount /usr/vice as ext2 instead. > > -- > > Christopher 'Ducky' Chapin [EMAIL PROTECTED] > Unix Systems Administrator - Qualcomm, Inc. (858) 651-5433 > IT Host Services > > _______________________________________________ > OpenAFS-info mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-info > _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
