Mike, The message "too many mounted filesystems" could be the key equation. If you don't limit your host to the amount of information obtained by other machines when they are mounting your machine, then you can inadvertently create an infinite loop of mountees. Fortunately, Linux OS usually avoids this, therefore you need to create and compensate to rectify the situation. There is a file usually located in the /etc directory called exports. What it contains varies (read: man exports). Below is an example of an essential basic configuration. / receiving_host(rw,no_root_squash) /mnt/drive2 (noaccess) The first line allows the "receiving_host" (which you need to supply) to mount your entire file-system. The second line prevents any machine from mounting what maybe the very file-system they have on their machine. ************************************************************************* Signed, Grateful to Help _____________________________Reply_Separator_____________________________ Kaz Kylheku wrote: > On Wed, 16 Dec 1998, Mike Ogden wrote: > > > > > I get the following error > > --- > > VFS: unable to read Xenix/SystemV/Coherent superblock on device 16:01 > > mount: wrong fs type, bad option, bad superblock on /dev/hdc1 > > or too many mounted filesystems. > > Maybe the superblock really is bad. Do you have an actual Xenix system that can > mount the disk? When was the last time you were able able to successfully mount > that filesystem? > > - > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
