On Mon, May 02, 2005 at 05:30:18PM -0400, Daniel Savard wrote:
> I read somewhere in the manuals the filesystem which hold the Coda
> partitions shouldn't be fscked. I ran into a problem recently and I
> finally discovered this was because the server refused to mount the
> partition's filesystem because it was not fscked.
> 
> So, I fscked it and mounted it and everything seems to work.
> 
> HOWEVER, I must specify this partition didn't hold yet any files, so, my
> question is: Should we fsck or not the Coda partition's filesystems at
> boot time or when running into filesystem problems?

Yes, I think that the 'do not fsck' advise still stems from the time
that Coda used a custom inodefs to store the container files. Of course
if you use a raw partition for RVM, that partition doesn't contain a
valid filesystem and shouldn't be fsck'd.

Jan