From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: mount -tcoda /dev/cfs0 /mnt no longer works in -test9 and newer?
Date: Tue, 7 Nov 2000 13:48:42 -0500 [thread overview]
Message-ID: <20001107134841.A31058@cs.cmu.edu> (raw)
In-Reply-To: <20001106103539.A343@bug.ucw.cz>
In-Reply-To: <20001106103539.A343@bug.ucw.cz>; from pavel@suse.cz on Mon, Nov 06, 2000 at 10:35:39AM +0100
On Mon, Nov 06, 2000 at 10:35:39AM +0100, Pavel Machek wrote:
> Hi!
>
> It complains
>
> coda_read_super: Bad mount data
> coda_read_super: device index: 0
>
> and will not mount. What do I need to mount coda?
> Pavel
Miklos Szeredi sent a patch to support multiple mountpoints/coda
devices. However, the code falls back on the default device (cfs0)
when the mountdata is incorrect. So the problem must be unrelated
to the "Bad mount data" error message.
The code to mount with the correct mountdata looks like this:
#include <linux/coda.h>
muxfd = open("/dev/cfs0", O_RDWR);
struct coda_mount_data mountdata;
mountdata.version = CODA_MOUNT_VERSION;
mountdata.fd = muxfd
error = mount("coda", "/coda", "coda", MS_MGC_VAL,
(void *)&mountdata);
Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-07 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 9:35 mount -tcoda /dev/cfs0 /mnt no longer works in -test9 and newer? Pavel Machek
2000-11-07 18:48 ` Jan Harkes [this message]
2000-11-10 20:39 ` Pavel Machek
2000-11-10 21:48 ` [BUG] coda went from c 67 5 to c 67 0 [was Re: mount -tcoda /dev/cfs0 /mnt no longer works in -test9 and newer?] Pavel Machek
2000-11-10 21:27 ` Jan Harkes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001107134841.A31058@cs.cmu.edu \
--to=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox