On Thursday 30 August 2007 10:46, [EMAIL PROTECTED] wrote:
> Thank you! Now I do not think it is version problem. Actually, I found
> that the TCP connection is never complete between my nfs client and
> server. The server reply the SYN,ACK but the client just do not respond.
> As for UDP is the sa
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
件名
Re: mount:nfsmount failed: Bad file descriptor
On Wednesday 29 August 2007 03:42, [EMAIL PROTECTED] wrote:
> After I try busbox 1.6.1, the bad file descriptor error disappear, but
> still got RPC timeout error. And the mount s
On Wednesday 29 August 2007 03:42, [EMAIL PROTECTED] wrote:
> After I try busbox 1.6.1, the bad file descriptor error disappear, but
> still got RPC timeout error. And the mount service is still V1. I think it
Yes, strace was clearly showing that server doesn't respond.
If you still unsure what's
Vlasenko <[EMAIL PROTECTED]>
08/28/2007 06:56 PM
宛先
[EMAIL PROTECTED]
cc
busybox@busybox.net
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
件名
Re: mount:nfsmount failed: Bad file descriptor
On Tuesday 28 August 2007 04:33, [EMAIL PROTECTED] wrote:
> When use strace the log is look
L PROTECTED]" <[EMAIL PROTECTED]>
件名
Re: mount:nfsmount failed: Bad file descriptor
On Tuesday 28 August 2007 04:33, [EMAIL PROTECTED] wrote:
> When use strace the log is look like this:
>
> root# cat mount.log
> execve("/bin/mount", ["mount", &quo
On Tuesday 28 August 2007 04:33, [EMAIL PROTECTED] wrote:
> When use strace the log is look like this:
>
> root# cat mount.log
> execve("/bin/mount", ["mount", "-t", "nfs", "192.168.1.6:/opt/Qtopia_2",
> "/opt/Qtopia_2"], [/* 10 vars */]) = 0
> uname({sys="Linux", node="imx21", ...}) = 0
> brk(0)
CTED]
件名
Re: mount:nfsmount failed: Bad file descriptor
On Monday 27 August 2007 08:48, [EMAIL PROTECTED] wrote:
> Hi,
>I have encoutered a problem when mount a nfs filesystem. The nfs
> server's ip is 192.168.1.6 and busybox version is 1.1.3. All the must
> configure fe
rite(2, ": Bad file descriptor\n", 22) = 22
write(2, "mount: ", 7) = 7
write(2, "Mounting 192.168.1.6:/opt/Qtopia"..., 58) = 58
write(2, ": Bad file descriptor\n", 22) = 22
_exit(1) = ?
When I use the same kern
On Monday 27 August 2007 08:48, [EMAIL PROTECTED] wrote:
> Hi,
>I have encoutered a problem when mount a nfs filesystem. The nfs
> server's ip is 192.168.1.6 and busybox version is 1.1.3. All the must
> configure features in busybox and kernel is turn on.
> CONFIG_FEATURE_MOUNT_NFS is set to y.
[EMAIL PROTECTED] wrote:
>
> Hi,
>I have encoutered a problem when mount a nfs filesystem. The nfs
> server's ip is 192.168.1.6 and busybox version is 1.1.3. All the must
> configure features in busybox and kernel is turn on.
> CONFIG_FEATURE_MOUNT_NFS is set to y. And kernel's config CONFI
Hi,
I have encoutered a problem when mount a nfs filesystem. The nfs
server's ip is 192.168.1.6 and busybox version is 1.1.3. All the must
configure features in busybox and kernel is turn on.
CONFIG_FEATURE_MOUNT_NFS is set to y. And kernel's config CONFIG_NFS_FS,
CONFIG_NFS_V3 are set to y.
11 matches
Mail list logo