Re: nfs problem

[Anders Andersson]

On Fri, Jan 1, 2016 at 10:30 PM, Glenn English  wrote:
> Come on folks!
>
> Consider a modified Drake equation: (number on this list) * (date) * (% not 
> hungover) * (% who understand NFS) * (% willing to help out a bewildered 
> computer geek) == (surely > 0), no?
>
> OK. Leave out (date) and (% not hungover), and tell me what I've done wrong...
>
>> On Dec 31, 2015, at 4:56 PM, ghe  wrote:
>>
>> I'm trying to get NFS going with a Wheezy server and a Jessie client using 
>> Webmin and vi. It connects, but mounts the directory and file with 
>> nobody:nogroup as the user:group (and nobody isn't set to universe 
>> read/write -- tried to do that, but NFS won't let me).
>>
>> I see from the 'Net that this is a common problem, but the solutions seem to 
>> involve (some) files/programs that don't exist on these machines. Nor in 
>> Aptitude.
>>
>> The UID:GID are identical on the server and the client, both numbers and 
>> text. I've tried both NFS4 and vanilla NFS. There seems to be no difference.
>>
>> I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and created a 
>> new user (gheqw). Now ls says the directory on the client is owned by 
>> gheqw:nogroup. That doesn't make any sense to me at all.
>>
>> When I turn off the NFS mount at the server, the directory on the client 
>> goes back to being owned by me, and the file disappears (both expected 
>> behavior).
>>
>> There are too many variables here: 2 computers, many files, and far too many 
>> [SOLVED] pages on the 'Net. I'm pretty sure I've made a mess in the config 
>> files (whichever they are). Anybody know exactly what to say, in which 
>> file(s) on which computer(s), to deal with this?


Ok, I have a couple of suggestions, which should not necessarily be
implemented in this order. :)

1) Ditch webmin, I don't know what it is but it seems to break
something that should be pretty simple to set up, without giving any
feedback.
2) If the problem involves some files that do not exist, please list
them, maybe it's a clue that something important is missing.
3) NFS is well documented in the man-pages, but has a pathetic
documentation online. Try "man nfs" and "man exports".
4) As somone else mentioned, do not mess with idmapd, since you have
the UIDs synced already.
5) Until a few weeks ago my main NFS server was wheezy, but I am now
using stretch. My files looks like this:

On the (stretch) server: /etc/exports contains:
/srv/stuff   1.2.3.0/24(sec=sys,rw,no_subtree_check,mp,root_squash)

On the (jessie) clients: /etc/fstab contains:
name_of_server:/srv/stuff  /stuff  nfs4 _netdev,rw,auto,bg

You shouldn't have to change any other files, really, but I can't
remember if this has something that's not supported on wheezy.

Re: nfs problem

[Glenn English]

> On Jan 1, 2016, at 4:41 PM, Pier  wrote:
> 
> It was ages I didn't write to the list but nfs always arouse curiosity ;)
> First try to force nfsv3 to see if permissions are ok (v3 uses numeric 
> uid/gid) with 'mount -o vers=3'.
> If this works and you want to use nfsv4 then make sure the configuration of 
> idmap are the same on both the nfs server and nfs client (make sure the 
> domain is the same, you can leave the rest the original).
> Also make sure the users/groups are available/the same on both the nfs 
> server/client.
> 
> Hope this helps.

So do I :-) I'm fine with v3. I'll try them.

-- 
Glenn English

Re: nfs problem

[Glenn English]

> On Jan 2, 2016, at 2:56 AM, Anders Andersson  wrote:
> 
> 1) Ditch webmin, I don't know what it is but it seems to break
> something that should be pretty simple to set up, without giving any
> feedback.

Webmin's one of those web-based GUI admin things. I use it because it usually 
does well, and it makes many configs quite a bit easier. It saved my life many 
times when I first hit Linux and IP networking.

In the past, Webmin's managed to make NFS work for me, but this seems to be one 
of those probs that require vi and a plea to the list...

> 2) If the problem involves some files that do not exist, please list
> them, maybe it's a clue that something important is missing.

I've looked at so many on the 'Net that I don't remember where I looked or what 
they were.

> 3) NFS is well documented in the man-pages, but has a pathetic
> documentation online. Try "man nfs" and "man exports".

Done, looks hopeful.

> 4) As somone else mentioned, do not mess with idmapd, since you have
> the UIDs synced already.

I'll put its config back to where it was :-)

> 5) Until a few weeks ago my main NFS server was wheezy, but I am now
> using stretch. My files looks like this:
> 
> On the (stretch) server: /etc/exports contains:
> /srv/stuff   1.2.3.0/24(sec=sys,rw,no_subtree_check,mp,root_squash)
> 
> On the (jessie) clients: /etc/fstab contains:
> name_of_server:/srv/stuff  /stuff  nfs4 _netdev,rw,auto,bg
> 
> You shouldn't have to change any other files, really, but I can't
> remember if this has something that's not supported on wheezy.

Very useful info -- different from what Webmin wrote. I'm a bit far from having 
an NFS export mounted at boot, though. When it works by hand, I'll put it in.

Thank you, Anders. 

-- 
Glenn English

Re: nfs problem

[Glenn English]

> On Jan 1, 2016, at 3:11 PM, Brandon Vincent  wrote:
> 
> I would return the server's idmapd.conf back to the default
> configuration (nobody:nogroup) and make sure that the idmapd service
> is running on both the server and the client. Make sure the domain
> matches in idmapd.conf on both the server and client.

Hmmm. Nobody told me before that I needed idmapd on both ends. Bears looking 
into. Thanks.

-- 
Glenn English

Re: nfs problem [FIXED?]

[ghe]

On 01/02/2016 10:06 AM, Glenn English wrote:

Beats me, but it's working.

I modified the line in /etc/exports (all on one line) to:

/home/ghe/Finances 
192.168.3.0/255.255.255.0(rw,no_root_squash,no_subtree_check)


That isn't exactly as suggested, but there were mild complaints about 
not having anything about subtree_check.


and in fstab on the client:

sbox.slsware.lan:/home/ghe/Finances
/home/ghe/Finances  nfs user,nfsvers=3,exec,_netdev00

I'm thinking that 'nfsvers=3' might have done it, or maybe hand writing 
the export line containing the dotted quads for the IP/mask. Or maybe 
that I printed many pages of documentation. I really don't know; it just 
magically started working. I hate it when variables > 1.


Anyway, thank you all. I got my gnucash file in one place, on one 
server, but available to me everywhere on the LAN. And the next file 
will be a whole lot easier...


--
Glenn English

Re: nfs problem

[Brandon Vincent]

On Thu, Dec 31, 2015 at 4:56 PM, ghe  wrote:
> I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and created a
> new user (gheqw). Now ls says the directory on the client is owned by
> gheqw:nogroup. That doesn't make any sense to me at all.

I would return the server's idmapd.conf back to the default
configuration (nobody:nogroup) and make sure that the idmapd service
is running on both the server and the client. Make sure the domain
matches in idmapd.conf on both the server and client.

Brandon Vincent

Re: nfs problem

[Pier]

On Friday, 1 January 2016, 21:57, Glenn English  wrote:



 Come on folks!

Consider a modified Drake equation: (number on this list) * (date) * (% not 
hungover) * (% who understand NFS) * (% willing to help out a bewildered 
computer geek) == (surely > 0), no?

OK. Leave out (date) and (% not hungover), and tell me what I've done wrong...

> On Dec 31, 2015, at 4:56 PM, ghe  wrote:
> 
> I'm trying to get NFS going with a Wheezy server and a Jessie client using 
> Webmin and vi. It connects, but mounts the directory and file with 
> nobody:nogroup as the user:group (and nobody isn't set to universe read/write 
> -- tried to do that, but NFS won't let me).
[big cut]
It was ages I didn't write to the list but nfs always arouse curiosity ;)First 
try to force nfsv3 to see if permissions are ok (v3 uses numeric uid/gid) with 
'mount -o vers=3'.If this works and you want to use nfsv4 then make sure the 
configuration of idmap are the same on both the nfs server and nfs client (make 
sure the domain is the same, you can leave the rest the original).Also make 
sure the users/groups are available/the same on both the nfs server/client.
Hope this helps.
Pier
PS: you can check which version of nfs is used in /proc/mounts

   

Re: nfs problem

[Glenn English]

Come on folks!

Consider a modified Drake equation: (number on this list) * (date) * (% not 
hungover) * (% who understand NFS) * (% willing to help out a bewildered 
computer geek) == (surely > 0), no?

OK. Leave out (date) and (% not hungover), and tell me what I've done wrong...

> On Dec 31, 2015, at 4:56 PM, ghe  wrote:
> 
> I'm trying to get NFS going with a Wheezy server and a Jessie client using 
> Webmin and vi. It connects, but mounts the directory and file with 
> nobody:nogroup as the user:group (and nobody isn't set to universe read/write 
> -- tried to do that, but NFS won't let me).
> 
> I see from the 'Net that this is a common problem, but the solutions seem to 
> involve (some) files/programs that don't exist on these machines. Nor in 
> Aptitude.
> 
> The UID:GID are identical on the server and the client, both numbers and 
> text. I've tried both NFS4 and vanilla NFS. There seems to be no difference.
> 
> I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and created a 
> new user (gheqw). Now ls says the directory on the client is owned by 
> gheqw:nogroup. That doesn't make any sense to me at all.
> 
> When I turn off the NFS mount at the server, the directory on the client goes 
> back to being owned by me, and the file disappears (both expected behavior).
> 
> There are too many variables here: 2 computers, many files, and far too many 
> [SOLVED] pages on the 'Net. I'm pretty sure I've made a mess in the config 
> files (whichever they are). Anybody know exactly what to say, in which 
> file(s) on which computer(s), to deal with this?
> 
> T much IA...
> 
> -- 
> Glenn English

-- 
Glenn English

nfs problem

[ghe]

I'm trying to get NFS going with a Wheezy server and a Jessie client 
using Webmin and vi. It connects, but mounts the directory and file with 
nobody:nogroup as the user:group (and nobody isn't set to universe 
read/write -- tried to do that, but NFS won't let me).


I see from the 'Net that this is a common problem, but the solutions 
seem to involve (some) files/programs that don't exist on these 
machines. Nor in Aptitude.


The UID:GID are identical on the server and the client, both numbers and 
text. I've tried both NFS4 and vanilla NFS. There seems to be no difference.


I changed the nobody name to myself (ghe) in /etc/idmapd.conf, and 
created a new user (gheqw). Now ls says the directory on the client is 
owned by gheqw:nogroup. That doesn't make any sense to me at all.


When I turn off the NFS mount at the server, the directory on the client 
goes back to being owned by me, and the file disappears (both expected 
behavior).


There are too many variables here: 2 computers, many files, and far too 
many [SOLVED] pages on the 'Net. I'm pretty sure I've made a mess in the 
config files (whichever they are). Anybody know exactly what to say, in 
which file(s) on which computer(s), to deal with this?


T much IA...

--
Glenn English

Re : nfs problem

[Stephane Durieux]

Strangely, putting a dns for the local zone (and forwarder for the rest) 
improves the situation.
No cannot monitor in kern.log anymore ...




De : Bob Proulx b...@proulx.com
À : debian-user@lists.debian.org
Envoyé le : Mardi 20 Septembre 2011 21h46
Objet : Re: nfs problem

Stephane Durieux wrote:
 I have messages like this in logs: 
 lockd cannot monitor ip_address
 and also messages about statd 

The lockd: cannot monitor messages are due to the kernel being unable
to communicate with the rpc.statd process.  That usually indicates
that the rpc.statd is not running, possibly due to it crashing.

NFS is a stateless protocol.  But file locks are inherently stateful.
To maintain file locks some auxilary programs are used such as the
rpc.statd.

Check that the rpc.statd is running.

  ps -e | grep rpc.statd

It is started from the nfs-common service.  You may have to restart
it.

  # service nfs-common restart

Problems with NFS locking has been a problem forever.

 But client ip are present in /etc/hosts.

This has nothing to do with host names or DNS resolution.

 Do I need to put a DNS server for reverse resolution even for
 private ip, it s a pity

No.  Not for NFS.  But generally it is always a good idea that names
resolve to addresses and the reverse of resolving addresses to names
also works.

Bob

nfs problem

[Stephane Durieux]

Hello, 


I am encountering a problem with nfs on debian squeeze.

I have messages like this in logs: 

lockd cannot monitor ip_address

and also messages about statd 


But client ip are present in /etc/hosts.

On the client the mount process works.
The only problem is locking (application like firefox for example)

and when several stations are on the network, the collaspe begin


Has anybody an idea of what happens ?

Do I need to put a DNS server for reverse resolution even for private ip,  it s 
a pity 



Thanks

Re: nfs problem

[Bob Proulx]

Stephane Durieux wrote:
 I have messages like this in logs: 
 lockd cannot monitor ip_address
 and also messages about statd 

The lockd: cannot monitor messages are due to the kernel being unable
to communicate with the rpc.statd process.  That usually indicates
that the rpc.statd is not running, possibly due to it crashing.

NFS is a stateless protocol.  But file locks are inherently stateful.
To maintain file locks some auxilary programs are used such as the
rpc.statd.

Check that the rpc.statd is running.

  ps -e | grep rpc.statd

It is started from the nfs-common service.  You may have to restart
it.

  # service nfs-common restart

Problems with NFS locking has been a problem forever.

 But client ip are present in /etc/hosts.

This has nothing to do with host names or DNS resolution.

 Do I need to put a DNS server for reverse resolution even for
 private ip, it s a pity

No.  Not for NFS.  But generally it is always a good idea that names
resolve to addresses and the reverse of resolving addresses to names
also works.

Bob


signature.asc
Description: Digital signature

Re: nfs problem

[Jan Willem Stumpel]

Kurian Thayil wrote:
 Hi,
 
 If I can remember correctly. Include the option no_root_squash
 in /etc/exports of B. It will be like,
 
 /home/storage/video   A(rw,sync,subtree_check,no_root_squash)
 
 You will be able to read-write as root if you include this
 option.

This did not really work. To my amazement, the following drastic
simplification worked:

on B: /etc exports reads

/home/storage/video   A(async) C(async)

A user on the home net (desktop machine A or C) can mount, read,
and write the shared directory now.

nfs remains mysterious. But I am slowly gaining experience, now my
home has become 100% Debian (two desktops and a
gateway/server/firewall).

Regards, Jan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Mirco Piccin]

Hi,

 Machines A and B both run Debian. There are no firewall rules
 blocking any kind of traffic A--B.

 I try to mount, by means of nfs, a directory of B to a mount point
 on A, read-write.

 I can read the contents of /home/storage/video on B. But I cannot
 write anything to it. I keep getting the message read-only
 filesystem.

i'm not actual using NFS, but i remember that you must have the same
user and group id on both pc, or you will not able to do the job as
you describe.

hope this helps you!
Regards
M


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Kurian Thayil]

Hi,

If I can remember correctly. Include the option no_root_squash in
/etc/exports of B. It will be like,

/home/storage/video   A(rw,sync,subtree_check,no_root_squash)

You will be able to read-write as root if you include this option.


Regards,

Kurian Mathew Thayil.

On 10/30/08, Mirco Piccin [EMAIL PROTECTED] wrote:
 Hi,

 Machines A and B both run Debian. There are no firewall rules
 blocking any kind of traffic A--B.

 I try to mount, by means of nfs, a directory of B to a mount point
 on A, read-write.

 I can read the contents of /home/storage/video on B. But I cannot
 write anything to it. I keep getting the message read-only
 filesystem.

 i'm not actual using NFS, but i remember that you must have the same
 user and group id on both pc, or you will not able to do the job as
 you describe.

 hope this helps you!
 Regards
 M


 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nfs problem

[Jan Willem Stumpel]

Machines A and B both run Debian. There are no firewall rules
blocking any kind of traffic A--B.

I try to mount, by means of nfs, a directory of B to a mount point
on A, read-write.

/etc/exports in B has:
/home/storage/video   A(rw,sync,subtree_check)

/etc/fstab in A has:
B:/home/storage/video /mountB nfs \
user,rw,intr,rsize=8192,wsize=8192,timeo=14,noauto  0  0

If I call (on A)
   mount /mountB

I can read the contents of /home/storage/video on B. But I cannot
write anything to it. I keep getting the message read-only
filesystem.

I hope there are some nfs experts here who can shed some light.

Regards, Jan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS problem -- SOLVED!

[Ken Heard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Alex Samad put me on the right track to the solution.  See comments in
line below.

snip

 Other factors which may have a bearing on the situation:  the BDS
 computer is a P4; whereas the SOL is a dual core on a Foxconn
 motherboard.  Several other things do not work properly in SOL, such as
  mounting and unmounting CF cards; so I wonder if there is something
 wrong with the Foxconn BIOS.  There has been some noise on line recently
 about Foxconn's unfriendliness to Linux; for on Foxconn board model (not
 mine) somebody disected the BIOS and found out why.  When he raised the
 issue with Foxconn they were upset at being found out but did not care
 whether Linux worked with Foxconn boards or not.  Caveat emptor.
 
 I would be rather supprised if a boggy bios stopped nfs mounting, as long
 as ping and other ip was working okay.

Yes, true in this case, but I think I still have issues respecting this
board and its BIOS -- subject for a separate thread perhaps.

snip again to the part of Alex's post which put me on the right track.

 Also have a look from each server to the other server with showmounts -e
 servername

I did not know about this command, which by the way is showmount, so I
read its man page.  Running showmount -e SOL on BDS returned the
directories exported from BDS, not those exported from SOL -- most
peculiar.  I then got the bright idea to run showmount -e
192.168.0.114, 114 being the IP address of the SOL box.  This time the
command returned the directories exported from SOL.  So what it going on?

By running ifconfig in both boxes I verified their IP addresses.  I
checked the /etc/hosts file in both to verify that the right hostnames
were assigned to the right IP addresses.  They were.

I paid particular attention to the BDS:/etc/hosts file, because I
assumed that the problem must reside there.  Finally I noticed that the
 local loopback alias was SOL, not BDS.  The box now called BDS used to
be called SOL.  When I changed the name I changed the name assigned to
the IP address of the new BDS (old SOL) but had neglected to change the
loopback alias.  So I changed it, and BDS can now access the directories
exported from SOL.

I don't fully understand the loopback, but the fact that I had the
loopback alias wrong obviously explains why other things had not worked,
such as accessing html files from a browser using the alias rather than
localhost.

Thanks to Thomas P. and Alex S. for their help.

Regards,

Ken Heard



-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.0 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIkNLQlNlJzOkJmTcRAkyQAJ9XjDfyr+kSV74ksT6bNng2APu7zQCePnK2
d61lQ9w66qLgfN2CraL4Hzs=
=UdRM
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS problem -- SOLVED!

[Ken Heard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

And thanks also to Matthew M.  -- sorry Matthew.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.0 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIkNNElNlJzOkJmTcRAi6IAJ92a316VPCAh0E47K4+J6wadeBCbgCggba9
GThDY5qkC/DgJW3SOz6bQcs=
=1zh8
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS problem

[Ken Heard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

In response to my message of 2008-07-28 on this subject M. Preud'homme
rightly intimated that I should have provided more information so that
he (and others?) could help me.  So, here is the information he asked me
for, as well as the output of the strace mount -a command.

Both the subject computers use Etch.  One computer is named SOL, which
is used regularly by user ken; so all ken's user files are in SOL.  In
SOL the permissions for the directory /home/ken -- and all the
directories the next level down in /home/ken -- are drwxrwx---.

The other computer is called BDS, which is regularly used by user
martin; so all of his user files are in BDS.  In BDS the permissions for
the directory /home/martin -- and all the directories the next level
down in /home/martin -- are drwxrwx---.

In order for user martin to access his files on computer BDS by logging
in to computer SOL, file BDS:/etc/exports reads as follows:

/home/martin/docs   192.168.0.0/24(rw,no_subtree_check)
/home/martin/ice192.168.0.0/24(rw,no_subtree_check)
/home/martin/images-elph192.168.0.0/24(rw,no_subtree_check)
/home/martin/images-m   192.168.0.0/24(rw,no_subtree_check)

The output of command exportfs run on the BDS computer is consequently:

/home/martin/images-elph
192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534)

/home/martin/images-m
192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534)

/home/martin/docs
192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534)

/home/martin/ice
192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534)

In the SOL computer, the relevant lines of /etc/fstab are as follows:

# file system mount point   type  options   dump  pass
BDS:/home/martin/docs   /home/martin/docs   nfs
defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft  0   0
BDS:/home/martin/ice/home/martin/icenfs
defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft  0   0
BDS:/home/martin/images-elph/home/martin/images-elphnfs
defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft  0   0
BDS:/home/martin/images-m   /home/martin/images-m   nfs
defaults,noatime,bg,retry=1,rsize=8192,wsize=8192,soft  0   0

This arrangement works; martin, when logged on in SOL has access to his
files which physically are located in the BDS computer.  It is the
arrangement is the other direction which does not work.

File SOL:/etc/exports is as follows:

/home/ken/docs  192.168.0.0/24(rw,no_subtree_check)
/home/ken/images192.168.0.0/24(rw,no_subtree_check)
/home/ken/mozilla   192.168.0.0/24(rw,no_subtree_check)

The output of command exportfs run on the SOL computer is consequently:

/home/ken/mozilla   
192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534)

/home/ken/images
192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534)

/home/ken/docs  
192.168.0.0/24(rw,wdelay,root_squash,no_subtree_check,anonuid=65534,anongid=65534)

In the BDS computer, the relevant lines of /etc/fstab are as follows:

# file system mount point   type  options   dump  pass
SOL:/home/ken/docs  /home/ken/docs  nfs
defaults,noatime,bg,retry=5,rsize=8192,wsize=8192,soft  0   0   
SOL:/home/ken/mozilla   /home/ken/mozilla   nfs
defaults,noatime,bg,retry=5,rsize=8192,wsize=8192,soft  0   0

(I chose for the time being not to mount in BDS directory
SOL:/home/ken/images.)

Both SOL and BDS are turned off overnight.  BDS is usually booted first
the following morning; SOL is usually booted about three minutes later.
  Once both are booted, SOL can find the directories exported from BDS;
but BDS cannot find the directories exported from SOL.  I could find
nothing from the dmesg command or from the syslog file to relating to
the NFS.

After both computers have been booted but the export from SOL to BDS
does not work, I am able to ping successfully from one computer to the
other.  Running command mount -a from root however returns the following:

mount: none already mounted or /proc/bus/usb busy
mount: according to mtab, procbususb is already mounted on /proc/bus/usb
mount: SOL:/home/ken/docs failed, reason given by server: Permission denied
mount: SOL:/home/ken/mozilla failed, reason given by server: Permission
denied

The output of command strace mount -a is appended to the end of this
message after the horizontal line.  I cannot understand it; I hope it
means something useful for my problem to somebody.

Other factors which may have a bearing on the situation:  the BDS
computer is a P4; whereas the SOL is a dual core on a Foxconn
motherboard.  Several other things do not work properly in SOL, such as
 mounting and unmounting CF cards; so I wonder if there is something
wrong with the Foxconn BIOS.  There has been some noise on line recently
about 

Re: NFS problem

[Matthew Moore]

Hello,

You might try running

$ exportfs -r

on the host computer.

MM


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS problem

[Ken Heard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

As Matthew Moore suggested, after reading the relevant manual page to
see what command exportfs -r does, I ran on the server machine (SOL)
exportfs -rv, which returned the following:

exporting 192.168.0.0/24:/home/ken/mozilla
exporting 192.168.0.0/24:/home/ken/images
exporting 192.168.0.0/24:/home/ken/docs

I then ran on the client machine (BDS) mount -a.  Unfortunately is
returned the same message as before: mount failed: reason given by
server: permission denied.

Ken Heard
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.0 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIj4/PlNlJzOkJmTcRApTSAJ9n2tDLS4A67Zlt9opxsfMbMnqDjACfWx34
rL8dRERgvONCCIIXmct8Q+U=
=L/2P
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS problem

[Alex Samad]

some thoughts inline


On Tue, Jul 29, 2008 at 12:13:28PM -0400, Ken Heard wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 In response to my message of 2008-07-28 on this subject M. Preud'homme
 rightly intimated that I should have provided more information so that
 he (and others?) could help me.  So, here is the information he asked me
 for, as well as the output of the strace mount -a command.
 

[snip]

 Other factors which may have a bearing on the situation:  the BDS
 computer is a P4; whereas the SOL is a dual core on a Foxconn
 motherboard.  Several other things do not work properly in SOL, such as
  mounting and unmounting CF cards; so I wonder if there is something
 wrong with the Foxconn BIOS.  There has been some noise on line recently
 about Foxconn's unfriendliness to Linux; for on Foxconn board model (not
 mine) somebody disected the BIOS and found out why.  When he raised the
 issue with Foxconn they were upset at being found out but did not care
 whether Linux worked with Foxconn boards or not.  Caveat emptor.

I would be rather supprised if a boggy bios stopped nfs mounting, as long
as ping and other ip was working okay

 
 There are also other differences which I should not think contribute to
 the problem.  In SOL only the /home directories and files are encrypted.
  SOL uses the XFS file system; BDS has ext3.
 
 I apologize for the length of this message, but it was necessary to
 provide the requested information.  I hope it will be worthwhile.
 
 Regards, Ken Heard, Toronto, Canada
 -

[snip]

have you looked at /etc/hosts.allow and deny. check out
/var/log/auth.log and daemon.log.

Usually the only permissioning  problems are

access to the path I think full path access is need ie for an export of
/home/alex/test I would need access to /home and /home/alex and
/home/alex/test.

Another thing I do when trying to diagnose this is tcpdump, turn off all
the other mounts and start up tcpdump to capture the packets between the
servers. (u could also use wireshark or tshark)

Also have a look from each server to the other server with showmounts -e
servername


-- 
He understands the need for a timely write of the constitution.

- George W. Bush
04/28/2005
Washington, DC
on Prime Minister Iyad Allawi of Iraq


signature.asc
Description: Digital signature

NFS problem

[Ken Heard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I have two boxes, one normally used by user A, and the other by user B.
 I want to make it possible for user A to access his files from B's
computer, and vice versa.

So, in each computer I amended

1) file /etc/exports to export the relative directories and restarted
nfs-kernel-server, and

2) amended file /etc/fstab to mount the the directories exported from
the other computer in directores having the same name as the exported
ones and ran mount -a.

It is now possible for user A to log in on B's computer and see and use
his files, but not the reverse: B cannot log in on A's computer and use
his files.

What I find strange is that the nfs settings on both computers are
absolutely identical. Both computers use Etch.  The names and ids of
both users are the same; they both belong to the same group which has
identical name and id on both computers; and the permissions are the
same drwxrwx---.

One computer is a P4; the other is a dual core.  The export from the P4
to the dual core works; but the export from the dual core to the P4 does
not.  When I run mount -a on the P4 the following is returned for each
directory to be mounted:

failed, reason given by server:  Permission denied

After careful and extended experimentation I can't figure out why the
dual core cannot export.  I no one can provide me advice to point to
why, perhaps I should file a bug report.

Ken Heard


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.0 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIjiwblNlJzOkJmTcRAgGQAJwNSST44aBduivnWC4Al1Ss4DOYzgCfYIqp
SCig4eEYqwfhny1DIznlwDk=
=4Ftc
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS problem

[Thomas Preud'homme]

Le lundi 28 juillet 2008, Ken Heard a écrit :
 I have two boxes, one normally used by user A, and the other by user
 B. I want to make it possible for user A to access his files from B's
 computer, and vice versa.

 So, in each computer I amended

 1) file /etc/exports to export the relative directories and restarted
 nfs-kernel-server, and

 2) amended file /etc/fstab to mount the the directories exported from
 the other computer in directores having the same name as the exported
 ones and ran mount -a.

 It is now possible for user A to log in on B's computer and see and
 use his files, but not the reverse: B cannot log in on A's computer
 and use his files.

 What I find strange is that the nfs settings on both computers are
 absolutely identical. Both computers use Etch.  The names and ids of
 both users are the same; they both belong to the same group which has
 identical name and id on both computers; and the permissions are the
 same drwxrwx---.

Is it the permission of the directory you export ? And what about the 
rights of the file /etc/exports ?


 One computer is a P4; the other is a dual core.  The export from the
 P4 to the dual core works; but the export from the dual core to the
 P4 does not.  When I run mount -a on the P4 the following is returned
 for each directory to be mounted:

 failed, reason given by server:  Permission denied

Maybe a strace on the mount command will show something. Else please 
provide ls -al outputs of /etc/exports and the directory exported and 
directory where it is mounted.


 After careful and extended experimentation I can't figure out why the
 dual core cannot export.  I no one can provide me advice to point to
 why, perhaps I should file a bug report.

 Ken Heard

Regards

Thomas Preud'homme

-- 
Why Debian : http://www.debian.org/intro/why_debian


signature.asc
Description: This is a digitally signed message part.

nfs problem

[Ding Honghui]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

nfs server 192.168.110.28
FilesystemSize  Used Avail Use% Mounted on
/dev/sdb1 2.2T  1.6T  473G  78% /home

/etc/exports
/home/nfs_for_217  192.168.110.27/255.255.255.255 (rw,sync,no_root_squash)

nfs client
FilesystemSize  Used Avail Use% Mounted on
192.168.110.28:/home/nfs_for_217
  170G -417G  474G   -  /data_nfs218

What's the problem? The field Used is -417 and field Use% is -.
It's really strange..

thanks

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiEZ04ACgkQJo9Njjkvy372fgCffo9vfZra66+rRzkwiaFDeAre
Rn8AmwWST1LMI/Mknc51OSgjYauCAUrl
=ndad
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Bob McGowan]

Ding Honghui wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

nfs server 192.168.110.28
FilesystemSize  Used Avail Use% Mounted on
/dev/sdb1 2.2T  1.6T  473G  78% /home

/etc/exports
/home/nfs_for_217  192.168.110.27/255.255.255.255 (rw,sync,no_root_squash)

nfs client
FilesystemSize  Used Avail Use% Mounted on
192.168.110.28:/home/nfs_for_217
  170G -417G  474G   -  /data_nfs218

What's the problem? The field Used is -417 and field Use% is -.
It's really strange..

thanks

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiEZ04ACgkQJo9Njjkvy372fgCffo9vfZra66+rRzkwiaFDeAre
Rn8AmwWST1LMI/Mknc51OSgjYauCAUrl
=ndad
-END PGP SIGNATURE-




Sounds like a 32 vs. 64 bit int problem.  Perhaps NFS isn't using the 
proper type for holding the relevant information for df to read?


If you have access to a 64 bit capable system (laptop would be easiest, 
you could borrow for the test), you could boot using a live 64bit Debian 
CD, and do a mount of the NFS filesystem there.


I expect it would show the proper sizes.

--
Bob McGowan


smime.p7s
Description: S/MIME Cryptographic Signature

Re: nfs problem while internet access broken

[Stephane Durieux]

--- Bob Proulx [EMAIL PROTECTED] a écrit :

 Stephane Durieux wrote:
   client - server -X- internet 
  
  That is exactly my issue . Excuse me for not being
  clear ! Anyway, has somebody a solution .
  I have read that client and server must be able to
  make a reverse resolution of the client and the
  server, but I am not sure of it and I don t have
 an in
  depth knowledge of nfs . 
 
 The nfs server will try to do a dns lookup of the
 client ip address to
 find the client hostname for the purpose of logging
 this information
 to the system logs.  One the server can the client
 IP address be
 resolved?
 
   $ ssh server
   $ host A.B.C.D   # look up client IP address
 
 Does that succeed?  Example:
 
   $ ssh www.example.com
   host 208.77.188.166
   166.188.77.208.in-addr.arpa domain name pointer
 www.example.com.
 
 I suspect that your DNS on the server is not
 functioning.
 

I have noticed that my clients are not declared in
/etc/hosts if I put them in /etc/hosts (and in nis
table to be useful) everything is find.

Nevertheless I don t understand how the nfs can make a
resolution via dns of a a client whith a private
address 
Perhaps does the server reply it it s impossible and
everything is fine to log it 

But thanks a lot, it s certainly the SYSTEM LOG that
is implied ... I ll check it ... ...now it seems me a
little bit more logical !

I was so lost that I have thought they were magical
dark spirits behind this :) 
 



  
_ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Douglas Allan Tutty]

On Fri, Aug 03, 2007 at 02:47:14PM +0200, Stephane Durieux wrote:
 
 I have noticed that my clients are not declared in
 /etc/hosts if I put them in /etc/hosts (and in nis
 table to be useful) everything is find.
 
 Nevertheless I don t understand how the nfs can make a
 resolution via dns of a a client whith a private
 address 
 Perhaps does the server reply it it s impossible and
 everything is fine to log it 
 

/etc/nsswitch.conf (name service switch conf) has the line:
hosts:  files  dns

This means that when the resolver tries to find a host it will first
look in the files on the system (e.g. /etc/hosts) before doing a dns
search.

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Bob Proulx]

Stephane Durieux wrote:
 I have noticed that my clients are not declared in
 /etc/hosts

They won't need to be if you use DNS.  But it is acceptable to list
them in the local files.  Local files override network DNS.

 if I put them in /etc/hosts (and in nis table to be useful)
 everything is find.

You should not need to put hosts in NIS/YP and I recommend against it.
NIS/YP for host information is obsolete.  It is a holdover from before
DNS became the dominant protocol.  Having the same data in both places
means that they can get out of sync and that leads to confusion.  The
DRY principle here is don't repeat yourself.

 Nevertheless I don t understand how the nfs can make a
 resolution via dns of a a client whith a private
 address 

The NFS mountd will call gethostbyaddr(3).

  man 3 gethostbyaddr

If the information is not available it will fail.  But if dns is not
available it will timeout trying to look it up.

 Perhaps does the server reply it it s impossible and
 everything is fine to log it 

Many server processes will look up client ip addresses that connect
and try to log the name.

Bob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Stephane Durieux]

--- Douglas Allan Tutty [EMAIL PROTECTED] a écrit
:

 On Wed, Aug 01, 2007 at 11:00:19AM -0600, Bob Proulx
 wrote:
  Stephane Durieux wrote:
   Of course the network connexion is good !
   I can ping the server 
  
  But you said that the server cannot access the
 network:
 I encounter a problem whith my nfs stations.
  If the server has
 not access to internet, they cannot mount
 their directories !
  
  This is a contradiction.  You say that the server
 cannot connect to
  the internet and you say that you can ping your
 server.  Please
  explain.
  
 
 I think what he means is that:
 
   client  - server - internet
 
 Client can ping server but if server is not
 connected to internet,
 client can not mount nfs shares from server.
 
 Doug.

 client - server -X- internet 

That is exactly my issue . Excuse me for not being
clear ! Anyway, has somebody a solution .
I have read that client and server must be able to
make a reverse resolution of the client and the
server, but I am not sure of it and I don t have an in
depth knowledge of nfs . 

Thanks for reply
 
 


  
_ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Douglas Allan Tutty]

On Thu, Aug 02, 2007 at 01:46:40PM +0200, Stephane Durieux wrote:
 --- Douglas Allan Tutty [EMAIL PROTECTED] a ?crit
  I encounter a problem whith my nfs stations.
   If the server has
  not access to internet, they cannot mount
  their directories !
   
  I think what he means is that:
  
  client  - server - internet
  
  Client can ping server but if server is not
  connected to internet,
  client can not mount nfs shares from server.
  
  client - server -X- internet 
 
 That is exactly my issue . Excuse me for not being
 clear ! Anyway, has somebody a solution .
 I have read that client and server must be able to
 make a reverse resolution of the client and the
 server, but I am not sure of it and I don t have an in
 depth knowledge of nfs . 
 

With the internet off, check:

ping from client to server by name
ping from server to client by name

Send us /etc/hosts, /etc/host.conf, /etc/hosts.*, /etc/nsswitch.conf

Do you have a firewall that perhaps is changing config depending on
internet status?  What firewall do you use?

Relavent error messages:

1.  take a copy of /var/log/syslog on each machine.
2.  Try to mount an NFS directory
3.  Record any visible error messages on either box
4.  Take another copy of /var/log/syslog on each machine and diff
with the previous copy, and send the diffs, snipping off
extraneous or sensitive data.

Good luck,

Doug.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Bob Proulx]

Stephane Durieux wrote:
  client - server -X- internet 
 
 That is exactly my issue . Excuse me for not being
 clear ! Anyway, has somebody a solution .
 I have read that client and server must be able to
 make a reverse resolution of the client and the
 server, but I am not sure of it and I don t have an in
 depth knowledge of nfs . 

The nfs server will try to do a dns lookup of the client ip address to
find the client hostname for the purpose of logging this information
to the system logs.  One the server can the client IP address be
resolved?

  $ ssh server
  $ host A.B.C.D   # look up client IP address

Does that succeed?  Example:

  $ ssh www.example.com
  host 208.77.188.166
  166.188.77.208.in-addr.arpa domain name pointer www.example.com.

I suspect that your DNS on the server is not functioning.

Bob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nfs problem while internet access broken

[Stephane Durieux]

Hello 

I encounter a problem whith my nfs stations.
If the server has not access to internet, they cannot
mount their directories !

I have checked /etc/fstab
nfs server is referenced by is ip

/etc/nsswitch.conf
files hosts dns nis

/etc/host.conf 
order hosts, bind, nis

(I would like to know the difference between the two
lasts)

I ve heard it can be a reverse resolution problem. 
Can someone explain me it ? 
What is the file involved in reverse resolution
locally ?

Thanks for reply


  
_ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Andrew Sackville-West]

On Wed, Aug 01, 2007 at 05:51:40PM +0200, Stephane Durieux wrote:
 Hello 
 
 I encounter a problem whith my nfs stations.
 If the server has not access to internet, they cannot
 mount their directories !

in what way is network access broken? 

 
 I have checked /etc/fstab
 nfs server is referenced by is ip
 
 /etc/nsswitch.conf
 files hosts dns nis
 
 /etc/host.conf 
 order hosts, bind, nis

none of these matter if you have no network connection. If the local
machine cannot access any network then there is no way to mount nfs
shares. 

what is the output of 

/sbin/ifconfig

A


signature.asc
Description: Digital signature

Re: nfs problem while internet access broken

[Stephane Durieux]

--- Andrew Sackville-West
[EMAIL PROTECTED] a écrit :

 On Wed, Aug 01, 2007 at 05:51:40PM +0200, Stephane
 Durieux wrote:
  Hello 
  
  I encounter a problem whith my nfs stations.
  If the server has not access to internet, they
 cannot
  mount their directories !
 
 in what way is network access broken? 
 
  
  I have checked /etc/fstab
  nfs server is referenced by is ip
  
  /etc/nsswitch.conf
  files hosts dns nis
  
  /etc/host.conf 
  order hosts, bind, nis
 
 none of these matter if you have no network
 connection. If the local
 machine cannot access any network then there is no
 way to mount nfs
 shares. 
 
 what is the output of 
 
 /sbin/ifconfig
 
 A
 
Of course the network connexion is good !
I can ping the server 




  
_ 
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Bob Proulx]

Stephane Durieux wrote:
 Of course the network connexion is good !
 I can ping the server 

But you said that the server cannot access the network:
   I encounter a problem whith my nfs stations.  If the server has
   not access to internet, they cannot mount their directories !

This is a contradiction.  You say that the server cannot connect to
the internet and you say that you can ping your server.  Please
explain.

Bob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem while internet access broken

[Douglas Allan Tutty]

On Wed, Aug 01, 2007 at 11:00:19AM -0600, Bob Proulx wrote:
 Stephane Durieux wrote:
  Of course the network connexion is good !
  I can ping the server 
 
 But you said that the server cannot access the network:
I encounter a problem whith my nfs stations.  If the server has
not access to internet, they cannot mount their directories !
 
 This is a contradiction.  You say that the server cannot connect to
 the internet and you say that you can ping your server.  Please
 explain.
 

I think what he means is that:

client  - server - internet

Client can ping server but if server is not connected to internet,
client can not mount nfs shares from server.

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: dd NFS problem

[Michelle Konzack]

Am 2006-05-15 19:25:43, schrieb Bjoern Schliessmann:
 Michelle Konzack wrote:
 
  Weil TCP fehlerkorrektur hat und UDP nicht
 
 Gibt's im UDP-Header plötzlich keine Prüfsumme mehr oder was genau
 meinst du damit?

Genau.  Fehlerhafte Pakete werden gedroped.  Das ist genau der Grund,
warum Streaming Application UDP verwenden.

Das ist auch der Grund warum NFS über UDP rund 9,5-10 MByte bei einem
100MBit Netzwerk schaft, bei TCP hingegen nur 7,2-8 MByte.

Bei keinen Dateien hatte ich bei UDP noch nee probleme, erst als ich
anfing Dateien von hunderten von MBytes zu transferieren hatte ich
bei NFS plötzlich mit UDP fehlerhafte Dateien.

Anm.: Zusätzliches SSH tunneling von NFS/TCP läßt die Geschwindigkeit
  noch mal zusammenfallen. Auf rund 6-6,5 MByte/Sekunde.

Ich habe in meiner fstab als Optionen:

rw,bg,hard,intr,tcp,vers=3,rsize=8192,wsize=8192

seit Woody und 2.4.24 (vers=3 funktionierte erst ab diesem Kernel)
und keine Probleme mehr. Allerdings habe ich festgestellt, das
2.4.32 irgendwie schneller ist...

Greetings
Michelle Konzack


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/6/6192519367100 Strasbourg/France   IRC #Debian (irc.icq.com)


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: dd NFS problem

[Bjoern Schliessmann]

Michelle Konzack wrote:

 Weil TCP fehlerkorrektur hat und UDP nicht

Gibt's im UDP-Header plötzlich keine Prüfsumme mehr oder was genau
meinst du damit?

Grüße,


Björn

-- 
BOFH excuse #176:

vapors from evaporating sticky-note adhesives


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: dd NFS problem

[Michelle Konzack]

Am 2006-05-09 16:05:54, schrieb Alexander Syring:

 Nicht wirklich weil ich lass meinen nfs jetzt auch Version 3 laufen muss 
 keine 
 option vers=3 angeben und tcp brauch ich auch nicht. NFS ist doch gut und 
 schnell über udp warum soll ich dann tcp benutzen mit dem ganzen 
 zurückgeschicke von den ACKs.

Weil TCP fehlerkorrektur hat und UDP nicht, desweiteren
kann man UDP nicht SSH tunneln sondern nur TCP...

 UDP und TCP unterschied wird in einem Netzwerk mit Netzwerk-HUB (so nen altes 
 ding mit kollisionen und so)  deutlich. Denn UDP = bessere 
 übertragungsgeschw. weil weniger kollisionen. tcp die kollisionslampe am hub 
 will fast nicht mehr aus gehen = schlechtere geschw.

Tja, ich hatte egal in welchem netzwerk (10/100/1000 und switch/hub)
zu viele md5sum fehler bei UDP gehabt... Ich bekomme bei TCP rund
8 MByte/Sekunde mit 100MBit sowie 72 MByte/Sekunde bei GBit.

Denke nicht, das ich mich zu beklagen habe.

 Grüße 
 
 Alex

Greetings
Michelle Konzack


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: dd NFS problem

[Michelle Konzack]

Am 2006-05-03 19:46:28, schrieb Alexander Syring:
 Hi Liste
 ich hab ein Problem mit dd und nfs und zwar hab ich auf meinem laptop meinen 
 desktoprechner per NFS in /mnt/opteron eingebunden. Nun möchte ich eine 
 Partition von dem laptop komplett mit dd kopieren und gebe dazu ein:
 
 dd if=/dev/hda4 of=/mnt/opteron/test.img
 
 so funktionier alles wunderbar bis die datei test.img genau 2GB groß ist und 
 auf dem laptop die meldung steht die maximale dateigröße ist überschritten

mount -t nfs server /mnt/nfs -o 
rw,bg,hard,intr,tcp,vers=3,rsize=8192,wsize=8192

wird von mir verwendet und habe keine probleme,
mal so nebenbei 12 GByte zu transferieren.

Funktioniert nur bei tcp und vers=3

Greetings
Michelle Konzack


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: dd NFS problem

[Alexander Syring]

Am Sonntag, 7. Mai 2006 04:20 schrieb Michelle Konzack:
 Am 2006-05-03 19:46:28, schrieb Alexander Syring:
  Hi Liste
  ich hab ein Problem mit dd und nfs und zwar hab ich auf meinem laptop
  meinen desktoprechner per NFS in /mnt/opteron eingebunden. Nun möchte ich
  eine Partition von dem laptop komplett mit dd kopieren und gebe dazu ein:
 
  dd if=/dev/hda4 of=/mnt/opteron/test.img
 
  so funktionier alles wunderbar bis die datei test.img genau 2GB groß ist
  und auf dem laptop die meldung steht die maximale dateigröße ist
  überschritten

 mount -t nfs server /mnt/nfs -o
 rw,bg,hard,intr,tcp,vers=3,rsize=8192,wsize=8192

 wird von mir verwendet und habe keine probleme,
 mal so nebenbei 12 GByte zu transferieren.

 Funktioniert nur bei tcp und vers=3
   ^^^ behaupte ich was anderes

 Greetings
 Michelle Konzack
 [...]

Nicht wirklich weil ich lass meinen nfs jetzt auch Version 3 laufen muss keine 
option vers=3 angeben und tcp brauch ich auch nicht. NFS ist doch gut und 
schnell über udp warum soll ich dann tcp benutzen mit dem ganzen 
zurückgeschicke von den ACKs.

UDP und TCP unterschied wird in einem Netzwerk mit Netzwerk-HUB (so nen altes 
ding mit kollisionen und so)  deutlich. Denn UDP = bessere 
übertragungsgeschw. weil weniger kollisionen. tcp die kollisionslampe am hub 
will fast nicht mehr aus gehen = schlechtere geschw.

Grüße 

Alex

Re: dd NFS problem

[Bernd Schubert]

Alexander Syring wrote:

 Hi Liste
 ich hab ein Problem mit dd und nfs und zwar hab ich auf meinem laptop
 meinen desktoprechner per NFS in /mnt/opteron eingebunden. Nun möchte ich
 eine Partition von dem laptop komplett mit dd kopieren und gebe dazu ein:
 
 dd if=/dev/hda4 of=/mnt/opteron/test.img
 
 so funktionier alles wunderbar bis die datei test.img genau 2GB groß ist
 und auf dem laptop die meldung steht die maximale dateigröße ist
 überschritten
 
 so jetzt hatte ich nfs im verdacht aber ich kann ohne probleme dvd-images
 hin und her kopieren. Also sollte es dann an dd liegen doch das ist es
 auch nicht denn ich hab dd if=/dev/zero of=/test.img laufen lassen bis
 die platte voll war und das waren mehr als 2GB.
 
 Also wo liegt mein denkfehler oder was mache ich falsch?
 

Welcher NFS Server, welche NFS Version? NFSv2 kann nur bis 2GB und der
uralte Userspace Server kann nur NFSv2. Kernel-nfs und unfs3 können NFSv3.
In /proc/mounts steht welche Protokollversion verwendet wird.


Grüße,
Bernd


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: dd NFS problem (SOLVED)

[Alexander Syring]

Am Donnerstag, 4. Mai 2006 13:39 schrieb Bernd Schubert:
 Alexander Syring wrote:

 Welcher NFS Server, welche NFS Version? NFSv2 kann nur bis 2GB und der
 uralte Userspace Server kann nur NFSv2. Kernel-nfs und unfs3 können NFSv3.
 In /proc/mounts steht welche Protokollversion verwendet wird.


 Grüße,
 Bernd

OK daran hat es gelegen auf dem einen Rechner von dem ich große Dateien 
kopiert hat läuft auf nfs v3.
Auf'm Desktop läuft nfs v2 also werd ich da mal nen update machen müssen

danke

dd NFS problem

[Alexander Syring]

Hi Liste
ich hab ein Problem mit dd und nfs und zwar hab ich auf meinem laptop meinen 
desktoprechner per NFS in /mnt/opteron eingebunden. Nun möchte ich eine 
Partition von dem laptop komplett mit dd kopieren und gebe dazu ein:

dd if=/dev/hda4 of=/mnt/opteron/test.img

so funktionier alles wunderbar bis die datei test.img genau 2GB groß ist und 
auf dem laptop die meldung steht die maximale dateigröße ist überschritten

so jetzt hatte ich nfs im verdacht aber ich kann ohne probleme dvd-images hin 
und her kopieren. Also sollte es dann an dd liegen doch das ist es auch nicht 
denn ich hab dd if=/dev/zero of=/test.img laufen lassen bis die platte voll 
war und das waren mehr als 2GB.

Also wo liegt mein denkfehler oder was mache ich falsch?

Viele Grüße
Alex

Re: dd NFS problem

[Moritz Lenz]

Hallo,

Alexander Syring wrote:
[...]
 dd if=/dev/hda4 of=/mnt/opteron/test.img
 
 so funktionier alles wunderbar bis die datei test.img genau 2GB groß ist und 
 auf dem laptop die meldung steht die maximale dateigröße ist überschritten
 
 so jetzt hatte ich nfs im verdacht aber ich kann ohne probleme dvd-images hin 
 und her kopieren. Also sollte es dann an dd liegen doch das ist es auch nicht 
 denn ich hab dd if=/dev/zero of=/test.img laufen lassen bis die platte voll 
 war und das waren mehr als 2GB.

Schuss ins Blaue: gib dd mal eine große Blocksize, z.B.
dd bs=10M ...
oder so, vielleicht sind es ja einfach zu viele Blocks.

Grüße,
Moritz

-- 
Moritz Lenz
http://moritz.faui2k3.org/



signature.asc
Description: OpenPGP digital signature

Re: dd NFS problem

[Alexander Syring]

Am Mittwoch, 3. Mai 2006 19:59 schrieb Moritz Lenz:
 ...
  
 Schuss ins Blaue: gib dd mal eine große Blocksize, z.B.
 dd bs=10M ...
 oder so, vielleicht sind es ja einfach zu viele Blocks.

 Grüße,
 Moritz

Habs probiert macht aber leider wieder bei genau 2GB schluss mit der gleichen 
fehlermeldung

Grüße 
Alex

Re: dd NFS problem

[Wolf Wiegand]

Hallo,

Alexander Syring wrote:

 dd if=/dev/hda4 of=/mnt/opteron/test.img
 
 so funktionier alles wunderbar bis die datei test.img genau 2GB groß ist und 
 auf dem laptop die meldung steht die maximale dateigröße ist überschritten
 [...]
 Also sollte es dann an dd liegen doch das ist es auch nicht 
 denn ich hab dd if=/dev/zero of=/test.img laufen lassen bis die platte voll 
 war und das waren mehr als 2GB.

Hm, ich habe das hier gerade getestet: Laptop ist Debian Sid, Server ein
Sarge mit XFS, gemountet per NFSv3 über UDP, ich konnte ein 3GB-Image
auf dem NFS-Server erstellen. Kommt dd evtl. nicht mit /dev/hda4 klar?
Was ergibt

dd if=/dev/hda4 of=/dev/null bs=1024
dd if=/dev/zero of=/mnt/opteron/test.img bs=1K count=3GB

?

Wolf
-- 
Wieso bin ich der einzige, der immer Recht hat? (Dittsche)


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: dd NFS problem

[Wolf Wiegand]

Wolf Wiegand wrote:

 dd if=/dev/zero of=/mnt/opteron/test.img bs=1K count=3GB
^^
Da sollte MB stehen.

Wolf

-- 
Kreuzigt mich - aber Debian ist einfach deppensicher. Es lässt Deppen gegen 
eine Wand von Schwierigkeiten klatschen und langsam abtropfen. Wer die Tür 
findet, darf mitspielen - und so sieht das Spielzeug dann eben aus: Gut 
gepflegt. (Joerg Rossdeutscher)


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: mounting DVDs via NFS problem

[Piers Kittel]

Have fixed the problem as NFS can't export UDF filesystems so mounted 
the DVD as ISO9660 and it worked.  Will keep exportfs -a in mind 
though as sometimes it won't play back the DVD via NFS unless I play 
about with exportfs a lot.


Thanks!

Cheers - Piers

Darryl Clarke wrote:

On 21/01/06, Piers Kittel [EMAIL PROTECTED] wrote:

Hello all,

Am trying to mount a DVD drive via NFS and am having problems.  For
note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15
(hostname - mythtv) is the server.

I have this in my /etc/exports:

/media/cdrom0 192.168.1.2(ro,sync)

and 192.168.1.2 is in the /etc/hosts.allow.

If the DVD is not mounted, it works perfectly fine:

destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv
destiny:/mnt# df
Filesystem   1K-blocks  Used Available Use% Mounted on
snip
mythtv:/media/cdrom0   1829192   1547128184472  90% /mnt/mythtv
destiny:/mnt#

If I unmount the above, and then mount the DVD on mythtv:

mythtv:/home/piers# mount /cdrom
mythtv:/home/piers#

and try again on destiny, I get:

destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv
mount: mythtv:/media/cdrom0 failed, reason given by server: Permission
denied
destiny:/#

and in the logs, I get:

Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09)
Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000)
Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from
destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0)
Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted

I've googled for a long time with the last message but I can't find any
help anywhere.

I've tried this on my 2 Macs but had the exact same problem:

Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from
ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0)
Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted
Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from
akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0)
Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted

I'm hoping you guys can tell me what I'm doing wrong here?

Thanks very much in advance!


just a shot in the dark, you might have to 'exportfs -a' after
mounting your dvdrom to make the nfs server rehash the directory.

--
~ Darryl  ~ [EMAIL PROTECTED]
http://smartssa.com / http://darrylclarke.com




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: mounting DVDs via NFS problem

[Piers Kittel]

Andrew,

how can you mount a dvd over nfs if its not mounted on its local machine? Do these numbers above, as they come from destiny match the numbers if they are run on mythtv? IOW, are we looking at the same disk here? 


This bit is just to test if I can acutally mount it, i.e. I'm running 
the right commands, it all works etc - this confirms the problem 
orginates from mounting the DVD itself.  The numbers shows the hard 
drive sizes, as the cdrom directory is on the hard drive.



when you mount /cdrom on mythtv, do the permissions change? what is ls -l 
/cdrom when unmounted and mounted?


Yup you're correct, and have fixed this problem:

mythtv:/media# mount /cdrom
mythtv:/media# ls -l
total 2
lrwxrwxrwx  1 root   cdrom   6 2005-06-07 19:30 cdrom - cdrom0
dr-xr-xr-x  3 4294967295 4294967295 88 2003-09-08 21:08 cdrom0
mythtv:/media#

but if I do the following:

mythtv:/media# mount -o umask=000,uid=1000,gid=24 /dev/hdc /cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
mythtv:/media# ls -l
total 2
lrwxrwxrwx  1 root  cdrom  6 2005-06-07 19:30 cdrom - cdrom0
dr-xr-xr-x  3 piers cdrom 88 2003-09-08 21:08 cdrom0
mythtv:/media#

Works nicely, but still have the same problem:

Jan 23 11:23:13 localhost rpc.mountd: authenticated mount request from 
akane.10sca.intranet:956 for /media/cdrom0 (/media/cdrom0)

Jan 23 11:23:13 localhost rpc.mountd: getfh failed: Operation not permitted

Any ideas what I'm doing wrong?

Thanks very much for your help!

Regards - Piers


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: mounting DVDs via NFS problem

[Andrew Sackville-West]

On Mon, 23 Jan 2006 11:29:50 +
Piers Kittel [EMAIL PROTECTED] wrote:

 Andrew,
 
  how can you mount a dvd over nfs if its not mounted on its local machine? 
  Do these numbers above, as they come from destiny match the numbers if they 
  are run on mythtv? IOW, are we looking at the same disk here? 
 
 This bit is just to test if I can acutally mount it, i.e. I'm running 
 the right commands, it all works etc - this confirms the problem 
 orginates from mounting the DVD itself.  The numbers shows the hard 
 drive sizes, as the cdrom directory is on the hard drive.

oh yeah, okay.

 
  when you mount /cdrom on mythtv, do the permissions change? what is ls -l 
  /cdrom when unmounted and mounted?
 
 Yup you're correct, and have fixed this problem:
 
 mythtv:/media# mount /cdrom
 mythtv:/media# ls -l
 total 2
 lrwxrwxrwx  1 root   cdrom   6 2005-06-07 19:30 cdrom - cdrom0
 dr-xr-xr-x  3 4294967295 4294967295 88 2003-09-08 21:08 cdrom0
 mythtv:/media#
 
 but if I do the following:
 
 mythtv:/media# mount -o umask=000,uid=1000,gid=24 /dev/hdc /cdrom
 mount: block device /dev/hdc is write-protected, mounting read-only
 mythtv:/media# ls -l
 total 2
 lrwxrwxrwx  1 root  cdrom  6 2005-06-07 19:30 cdrom - cdrom0
 dr-xr-xr-x  3 piers cdrom 88 2003-09-08 21:08 cdrom0
 mythtv:/media#
 
 Works nicely, but still have the same problem:
 
 Jan 23 11:23:13 localhost rpc.mountd: authenticated mount request from 
 akane.10sca.intranet:956 for /media/cdrom0 (/media/cdrom0)
 Jan 23 11:23:13 localhost rpc.mountd: getfh failed: Operation not permitted

I have to ask just incase: can you mount other shares? /home/foo for example?

A


 
 Any ideas what I'm doing wrong?
 
 Thanks very much for your help!
 
 Regards - Piers
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 


pgpaM7TQaRTtl.pgp
Description: PGP signature

Re: mounting DVDs via NFS problem

[Darryl Clarke]

On 21/01/06, Piers Kittel [EMAIL PROTECTED] wrote:
 Hello all,

 Am trying to mount a DVD drive via NFS and am having problems.  For
 note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15
 (hostname - mythtv) is the server.

 I have this in my /etc/exports:

 /media/cdrom0 192.168.1.2(ro,sync)

 and 192.168.1.2 is in the /etc/hosts.allow.

 If the DVD is not mounted, it works perfectly fine:

 destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv
 destiny:/mnt# df
 Filesystem   1K-blocks  Used Available Use% Mounted on
 snip
 mythtv:/media/cdrom0   1829192   1547128184472  90% /mnt/mythtv
 destiny:/mnt#

 If I unmount the above, and then mount the DVD on mythtv:

 mythtv:/home/piers# mount /cdrom
 mythtv:/home/piers#

 and try again on destiny, I get:

 destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv
 mount: mythtv:/media/cdrom0 failed, reason given by server: Permission
 denied
 destiny:/#

 and in the logs, I get:

 Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09)
 Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000)
 Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from
 destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0)
 Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted

 I've googled for a long time with the last message but I can't find any
 help anywhere.

 I've tried this on my 2 Macs but had the exact same problem:

 Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from
 ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0)
 Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted
 Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from
 akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0)
 Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted

 I'm hoping you guys can tell me what I'm doing wrong here?

 Thanks very much in advance!

just a shot in the dark, you might have to 'exportfs -a' after
mounting your dvdrom to make the nfs server rehash the directory.

--
~ Darryl  ~ [EMAIL PROTECTED]
http://smartssa.com / http://darrylclarke.com

Re: mounting DVDs via NFS problem

[Andrew Sackville-West]

On Sat, 21 Jan 2006 22:04:25 +
Piers Kittel [EMAIL PROTECTED] wrote:

 Hello all,
 
 Am trying to mount a DVD drive via NFS and am having problems.  For 
 note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15 
 (hostname - mythtv) is the server.
 
 I have this in my /etc/exports:
 
 /media/cdrom0 192.168.1.2(ro,sync)
 
 and 192.168.1.2 is in the /etc/hosts.allow.
 
 If the DVD is not mounted, it works perfectly fine:
 
 destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv
 destiny:/mnt# df
 Filesystem   1K-blocks  Used Available Use% Mounted on
 snip
 mythtv:/media/cdrom0   1829192   1547128184472  90% /mnt/mythtv
 destiny:/mnt#

how can you mount a dvd over nfs if its not mounted on its local machine? Do 
these numbers above, as they come from destiny match the numbers if they are 
run on mythtv? IOW, are we looking at the same disk here? 


 
 If I unmount the above, and then mount the DVD on mythtv:
 
 mythtv:/home/piers# mount /cdrom
 mythtv:/home/piers#
 
 and try again on destiny, I get:
 
 destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv
 mount: mythtv:/media/cdrom0 failed, reason given by server: Permission 
 denied
 destiny:/#

when you mount /cdrom on mythtv, do the permissions change? what is ls -l 
/cdrom when unmounted and mounted?

A
 
 and in the logs, I get:
 
 Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) 
 Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000)
 Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from 
 destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0)
 Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted
 
 I've googled for a long time with the last message but I can't find any 
 help anywhere.
 
 I've tried this on my 2 Macs but had the exact same problem:
 
 Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from 
 ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0)
 Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted
 Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from 
 akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0)
 Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted
 
 I'm hoping you guys can tell me what I'm doing wrong here?
 
 Thanks very much in advance!
 
 Cheers - Piers
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 


pgpkDuxeXYAnI.pgp
Description: PGP signature

mounting DVDs via NFS problem

[Piers Kittel]

Hello all,

Am trying to mount a DVD drive via NFS and am having problems.  For 
note, 192.168.1.2 (hostname - destiny) is the client and 192.168.1.15 
(hostname - mythtv) is the server.


I have this in my /etc/exports:

/media/cdrom0 192.168.1.2(ro,sync)

and 192.168.1.2 is in the /etc/hosts.allow.

If the DVD is not mounted, it works perfectly fine:

destiny:/mnt# mount mythtv:/media/cdrom0 /mnt/mythtv
destiny:/mnt# df
Filesystem   1K-blocks  Used Available Use% Mounted on
snip
mythtv:/media/cdrom0   1829192   1547128184472  90% /mnt/mythtv
destiny:/mnt#

If I unmount the above, and then mount the DVD on mythtv:

mythtv:/home/piers# mount /cdrom
mythtv:/home/piers#

and try again on destiny, I get:

destiny:/# mount mythtv:/media/cdrom0 /mnt/mythtv
mount: mythtv:/media/cdrom0 failed, reason given by server: Permission 
denied

destiny:/#

and in the logs, I get:

Jan 21 21:57:08 localhost kernel: UDF-fs INFO UDF 0.9.8.1 (2004/29/09) 
Mounting volume 'FIREFLY_D3', timestamp 2003/09/08 20:08 (1000)
Jan 21 21:57:39 localhost rpc.mountd: authenticated mount request from 
destiny.10sca.intranet:923 for /media/cdrom0 (/media/cdrom0)

Jan 21 21:57:39 localhost rpc.mountd: getfh failed: Operation not permitted

I've googled for a long time with the last message but I can't find any 
help anywhere.


I've tried this on my 2 Macs but had the exact same problem:

Jan 21 20:34:55 localhost rpc.mountd: authenticated mount request from 
ukyo.10sca.intranet:982 for /media/cdrom0 (/media/cdrom0)

Jan 21 20:34:55 localhost rpc.mountd: getfh failed: Operation not permitted
Jan 21 21:29:59 localhost rpc.mountd: authenticated mount request from 
akane.10sca.intranet:972 for /media/cdrom0 (/media/cdrom0)

Jan 21 21:29:59 localhost rpc.mountd: getfh failed: Operation not permitted

I'm hoping you guys can tell me what I'm doing wrong here?

Thanks very much in advance!

Cheers - Piers


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS Problem? (Solved)

[Thomas Trueten]

Hallo Allerseits,
wie auch immer, ich habe aus meinem alten Ganten den Tip, bei Locking 
Problemen den NFS-Kernel-Server zu verwenden. Jetzt läufts, wenn auch die 
Performance des Kernel-Servers etwas schlechter ist.

 jetzt vom 
Am Samstag, 17. September 2005 16:58 schrieb Thomas Trueten:
 Hallo Allerseits,
 ich komme hier mit einem Problem nicht weiter:

 Die  /home Verzeichnisse liegen in meinem Netz auf einer XBOX. Diese läuft
 unter Xebian (Debian) Kernel 2.4.27 und werden per NFS exportiert.

 Auf den Clients läuft Debian (Knoppix 4.01, aktualisiert) mit Kernel 2.6.12

 Problematisch ist der Login in KDE 3.41: hier steigt der KDM aus. Starte
 ich KDE Programme z.B. unter icewm laufen diese problemlos.

 Hier mal eine Auskunft, so wie ich sehe, läuft auf der xbox nfs V2

 [EMAIL PROTECTED] nfsstat
 Client rpc stats:
 calls  retransauthrefrsh
 40202  20 0
 Client nfs v2:
 null   getattrsetattrroot   lookup readlink
 0   0% 15181  37% 15793% 0   0% 10102  25% 41  0%
 read   wrcachewrite  create remove rename
 9590   23% 0   0% 18724% 557 1% 566 1% 353 0%
 link   symlinkmkdir  rmdir  readdirfsstat
 125 0% 15  0% 14  0% 18  0% 184 0% 5   0%
 ---
 [EMAIL PROTECTED]  rpcinfo -p xbox
Program Vers Proto   Port
 102   tcp111  portmapper
 102   udp111  portmapper
 1000241   udp773  status
 1000241   tcp776  status
 132   udp   2049  nfs
 132   tcp   2049  nfs
 151   udp796  mountd
 152   udp796  mountd
 151   tcp799  mountd
 152   tcp799  mountd

 Syslog sagt:
 nsm_mon_unmon: rpc failed, status=-13
 lockd: cannot monitor 192.168.2.3
 lockd: failed to monitor 192.168.2.3

 Und dann noch die Meldung:
 nfs warning: mount version older than kernel

 Gegoogelt habe ich ausführlich, die Userids und Schreibrechte sind auf
 Clients und Server gleich bzw. erteilt.

-- 
Bonan tagon,
Thomas TruetenICQ# 82831959

PGP Key benötigt?  Leere Mail an: [EMAIL PROTECTED]
Fingerprint = EA28 D49D 6FEB CC33 A162 1777 2D94 693C 9042 62D1

NFS Problem?

[Thomas Trueten]

Hallo Allerseits,
ich komme hier mit einem Problem nicht weiter:

Die  /home Verzeichnisse liegen in meinem Netz auf einer XBOX. Diese läuft 
unter Xebian (Debian) Kernel 2.4.27 und werden per NFS exportiert. 

Auf den Clients läuft Debian (Knoppix 4.01, aktualisiert) mit Kernel 2.6.12

Problematisch ist der Login in KDE 3.41: hier steigt der KDM aus. Starte ich 
KDE Programme z.B. unter icewm laufen diese problemlos.

Hier mal eine Auskunft, so wie ich sehe, läuft auf der xbox nfs V2

[EMAIL PROTECTED] nfsstat
Client rpc stats:
calls  retransauthrefrsh
40202  20 0
Client nfs v2:
null   getattrsetattrroot   lookup readlink
0   0% 15181  37% 15793% 0   0% 10102  25% 41  0%
read   wrcachewrite  create remove rename
9590   23% 0   0% 18724% 557 1% 566 1% 353 0%
link   symlinkmkdir  rmdir  readdirfsstat
125 0% 15  0% 14  0% 18  0% 184 0% 5   0%
---
[EMAIL PROTECTED]  rpcinfo -p xbox
   Program Vers Proto   Port
102   tcp111  portmapper
102   udp111  portmapper
1000241   udp773  status
1000241   tcp776  status
132   udp   2049  nfs
132   tcp   2049  nfs
151   udp796  mountd
152   udp796  mountd
151   tcp799  mountd
152   tcp799  mountd

Syslog sagt:
nsm_mon_unmon: rpc failed, status=-13
lockd: cannot monitor 192.168.2.3
lockd: failed to monitor 192.168.2.3

Und dann noch die Meldung: 
nfs warning: mount version older than kernel

Gegoogelt habe ich ausführlich, die Userids und Schreibrechte sind auf Clients 
und Server gleich bzw. erteilt. 

-- 
Bonan tagon,
Thomas TruetenICQ# 82831959

PGP Key benötigt?  Leere Mail an: [EMAIL PROTECTED]
Fingerprint = EA28 D49D 6FEB CC33 A162 1777 2D94 693C 9042 62D1

Re: NFS problem with debian installation

[James Vahn]

On Mon, 25 Jul 2005, Michael Gass wrote:


I am having a problem with a debian install using nfs and a floppy boot.
I am trying to install woody (bf2.4 flavor) on an old 486 with 24M ram
(Compaq Prolinea 4/66).  I am using PLIP as the machine has no network
card and no cdrom.
.
  nfs: server 192.168.1.1 not responding, still trying


Sure sounds familiar.  What I did was to set up the host as an ftp or http
server and all was well, I think the latter easier to do than the former.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

NFS problem with debian installation

[Michael Gass]

I am having a problem with a debian install using nfs and a floppy boot.
I am trying to install woody (bf2.4 flavor) on an old 486 with 24M ram
(Compaq Prolinea 4/66).  I am using PLIP as the machine has no network
card and no cdrom.  This target machine is connected via PLIP to a source
machine (686 with 256M ram) running sarge (kernel 2.6).  The source
machine has a cdrom with the debian install cd.  The start of the 
installation goes fine: boot up with floppies and install driver floppies
and the the network.  Can ping the two machines.   The problem starts
with installing the base system - the initial nfs mount works and 
the target machine reads the file structure on the source machine (I
can tell since the the cdrom on the source is running). But after
reading in the cd file structure, the installer prompts for the
install directory (/instmnt).  When I accept the default, nfs dies.
dmesg on the target says 
   nfs: server 192.168.1.1 not responding, still trying
If I try to do ls on the target, it just hangs and the only thing
that I can do is reboot and start over.  Why is nfs dying at this point.
I have tried stopping and restarting the nfs-kernel-server on the 
source machine with no results.

Note: The above problem happens with the bf2.4 (2.4 kernel) flavor of
woody.  I can install the base system just fine with the vanilla 
(2.2 kernel) flavor of woody.  Any ideas?


-- 
Michael Gass
Department of Mathematics
St. John's University
Collegeville, MN  56321-3000
(320) 363-3090 
[EMAIL PROTECTED] 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

OT: NFS Problem (Text file busy)

[Hal Vaughan]

I'd put this on a Perl newsgroup, but when I Googled for more info, it came up 
that this is likely more of an NFS problem.  I could not find anything that 
could actually tell me how to fix it, though.

I have a server and a workstation.  I'm using Kate (for those who don't use 
it, it's a KDE text editor with a console visible in the window).  I access 
the files I'm working on in Kate through NFS.  In the console, I'm logged 
into the server through ssh.  I've used this setup on other systems (old 
Mandrake based systems) in the past, but now I'm using it on Debian based 
systems, so I think the problem is probably a setting I haven't found.

When I edit a Perl script in the text editor, and save it (through my NFS 
share), THEN try to run it through the console logged into the server through 
ssh, I get this error:

bash: /testing/tnet/bin/t-f1: /usr/bin/perl: bad interpreter: Text file busy

As best I can find out, this is related to NFS, but I don't recall getting 
error messages starting with bash: before, so I'm wondering if Bash is 
picking up something I don't know about.

If I wait 10-15 seconds, I can run the program.  Sometimes it seems to run 
after a shorter time.

Any ideas?

Thanks!

Hal


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bizarre NFS Problem

[Derek \The Monkey\ Wueppelmann]

On Tue, 2004-11-16 at 19:52, Tim Kelley wrote:
 Have you looked at tcpdump output while this is happening? you might see some 
 clues ...

I have done a TCP dump and it seems to be just fine, nothing is
different from a successful transfer then a failed transfer except at
the point it fails. The failure just ends the session and the successful
one continues.

 If you are using udp, just do
 
 tcpdump udp or icmp and port nfs
 
 You might see a lot of icmp error messages, and you'll certainly see the 
 fragmentation.
 
 You might try switching to tcp.  Most likely udp is the culprit here, since 
 any sort of network problem at all will result in data loss.  Tcp is not 
 noticeably slower and will work much better. On modern systems tcp and rsize 
 and wsize of 32k is pretty standard.

The above being said, how do I verify that I am using TCP and not UDP?

-- 
 o)  Derek Wueppelmann (o
(D .   [EMAIL PROTECTED]  D).
((`   http://www.monkeynet.ca/ ( ) `


signature.asc
Description: This is a digitally signed message part

Re: Bizarre NFS Problem

[Derek \The Monkey\ Wueppelmann]

On Fri, 2004-11-05 at 07:14, Ben Hutchings wrote:
 Derek The Monkey Wueppelmann wrote:
  Hello All,
  
  I'm currently running debian 3.0 r3 and have run into an interesting
  issue with my NFS mounts. On one of my debian systems (I have just done
  an apt-get update/upgrade on all my systems) when copying or creating a
  file on one of the NFS mounted directories I get an input/output error.
  The interesting thing is that this only happens for a file size of
  between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My
  mount point has been setup in fstab with the following options:
  
  rw,auto,soft,rsize=8192,wsize=8192
  
  Another interesting thing is that if I go to another of my debian
  systems that is running the exact same version of mount and nfs the copy
  works just fine. I am incredibly perplexed as to why this is happening,
  if anybody could shed some light on this that would be great.
 snip
 
 Perhaps it's something to do with IP fragmentation?  That works on 
 64-bit (8-byte) units so if there's some kind of bug in fragment 
 reassembly somewhere along the route then it might well affect fragments 
 in an 8-byte range of sizes.  See if the problem goes away if you reduce 
 the sizes to 1024, which should prevent fragmentation.  (This is bad for 
 performance so it's not a good solution, but it might help to identify 
 the source of the problem.)

I know this is an old thread now, but I finally got a chance to try out
the above. And while I was very hopeful in that it might work it still
ended up with the same results. I don't know about everybody else but I
am thoroughly puzzled by this.

-- 
 o)  Derek Wueppelmann (o
(D .   [EMAIL PROTECTED]  D).
((`   http://www.monkeynet.ca/ ( ) `


signature.asc
Description: This is a digitally signed message part

Re: Bizarre NFS Problem

[Tim Kelley]

On Tuesday 16 November 2004 08:45, Derek The Monkey Wueppelmann wrote:

 I know this is an old thread now, but I finally got a chance to try out
 the above. And while I was very hopeful in that it might work it still
 ended up with the same results. I don't know about everybody else but I
 am thoroughly puzzled by this.

Have you looked at tcpdump output while this is happening? you might see some 
clues ...

If you are using udp, just do

tcpdump udp or icmp and port nfs

You might see a lot of icmp error messages, and you'll certainly see the 
fragmentation.

You might try switching to tcp.  Most likely udp is the culprit here, since 
any sort of network problem at all will result in data loss.  Tcp is not 
noticeably slower and will work much better. On modern systems tcp and rsize 
and wsize of 32k is pretty standard.


-- 
  _   _   _   _   _   _   _   _   _   _   _   _   _  
 / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ 
( t | i | m | @ | i | t | . | k | p | t | . | c | c )
 \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ \_/ 
GPG key fingerprint = 1DEE CD9B 4808 F608 FBBF  DC21 2807 D7D3 09CA 85BF


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bizarre NFS Problem

[Ben Hutchings]

Derek The Monkey Wueppelmann wrote:
Hello All,
I'm currently running debian 3.0 r3 and have run into an interesting
issue with my NFS mounts. On one of my debian systems (I have just done
an apt-get update/upgrade on all my systems) when copying or creating a
file on one of the NFS mounted directories I get an input/output error.
The interesting thing is that this only happens for a file size of
between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My
mount point has been setup in fstab with the following options:
rw,auto,soft,rsize=8192,wsize=8192
Another interesting thing is that if I go to another of my debian
systems that is running the exact same version of mount and nfs the copy
works just fine. I am incredibly perplexed as to why this is happening,
if anybody could shed some light on this that would be great.
snip
Perhaps it's something to do with IP fragmentation?  That works on 
64-bit (8-byte) units so if there's some kind of bug in fragment 
reassembly somewhere along the route then it might well affect fragments 
in an 8-byte range of sizes.  See if the problem goes away if you reduce 
the sizes to 1024, which should prevent fragmentation.  (This is bad for 
performance so it's not a good solution, but it might help to identify 
the source of the problem.)

Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bizarre NFS Problem

[Derek \The Monkey\ Wueppelmann]

Hello All,

I'm currently running debian 3.0 r3 and have run into an interesting
issue with my NFS mounts. On one of my debian systems (I have just done
an apt-get update/upgrade on all my systems) when copying or creating a
file on one of the NFS mounted directories I get an input/output error.
The interesting thing is that this only happens for a file size of
between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My
mount point has been setup in fstab with the following options:

rw,auto,soft,rsize=8192,wsize=8192

Another interesting thing is that if I go to another of my debian
systems that is running the exact same version of mount and nfs the copy
works just fine. I am incredibly perplexed as to why this is happening,
if anybody could shed some light on this that would be great.

Just so everybody knows the command I'm using to create files on the NFS
system is:

dd if=/dev/urandom of=./test bs=1 count=4833

and it gives me the following error to the console:

4833+0 records in
4833+0 records out
dd: closing output file `./test': Input/output error

Although creating a file of the appropriate size and copying it would
cause the same result. Again just to re-iterate the weirdness is that if
I did the above command with a smaller value or a larger value it would
work. ie values of 4832, 4841, 8192, etc all work.

-- 
 o)  Derek Wueppelmann (o
(D .   [EMAIL PROTECTED]  D).
((`   http://www.monkeynet.ca/ ( ) `


signature.asc
Description: This is a digitally signed message part

Re: Bizarre NFS Problem

[Robert Parker]

On Thursday 04 November 2004 02:34, Derek \The Monkey\ Wueppelmann wrote:
 Hello All,

 I'm currently running debian 3.0 r3 and have run into an interesting
 issue with my NFS mounts. On one of my debian systems (I have just done
 an apt-get update/upgrade on all my systems) when copying or creating a
 file on one of the NFS mounted directories I get an input/output error.
 The interesting thing is that this only happens for a file size of
 between 4833-4840 inclusive or any multiple of 8192 + 4833-4840. My
 mount point has been setup in fstab with the following options:

I know nix about nfs but FWIW, after the just done update/upgrade everything 
went wierd on my Woody r3 box  until I rebooted it.

Might be worth a try.

Bob


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

NFS problem

[georg leugner]

hallo,
ich habe ein problem mit nfs.
also zuerst zu meinem client system debian testing mit kernel 2.6.7.
module die mit nfs zu tun haben könnten:
nfs
nfsd
exportfslockd
sunrpc
folgende dienste sind gestartet:
portmap
rpc.mountd
rpc.nfsd
rpc.statd
rpc.lockd
server: Fedora Core 2 ohne änderungen (sollte ansich auch richtig  
konfiguriert sein)

wenn ich nun den mount befehl eingebe
foo1 ist ein share mit folgenden attributen:  
(rw,insecure,sync,insecure_locks)
[EMAIL PROTECTED]:/mnt# mount 192.168.0.1:/mnt/foo1 /mnt/foo1/
kommt entweder:
eine meldung dass mein mount für meinen kernel zu alt sei.
(ich kanns lesen und mit einschränkungen beschreiben.)

oder ich bekomme nach dem mouten gar keine meldung, aber
foo2 hat attribute: (ro, sync)
[EMAIL PROTECTED]:/mnt# cd foo2/
[EMAIL PROTECTED]:/mnt/foo2# ls
ls: foo: Eingabe-/Ausgabefehler (foo ist in dem fall ein verzeichnis oder  
eine datei auf dem share; ich kann das objekt nich öffnen)
dmesg liefert in dem fall aber:
nfs_stat_to_errno: bad nfs status return value: 45

wenn ich zuerst foo2 mounte dann zeigt foo1 die selben symptome. ich muss  
auf dem client die services neustarten.
ich habe dann ein bisschen gegoogelt (und bin nach dem 1. error gegangen)  
und habe herausgefunden ich solle mein mount updaten. ich wollte dass dann  
auch machen, habe festgestellt dass ich nur mount-aes draufhabe und wenn  
ich mount stattdessen drauftue mein system schwer schädigen würde (ich  
habe mich nicht getraut).

mfg georg
--
where is my mind
--
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: NFS problem

[Michelle Konzack]

Hallo GEORG, 

Am 2004-07-12 15:31:41, schrieb georg leugner:
hallo,
ich habe ein problem mit nfs.
also zuerst zu meinem client system debian testing mit kernel 2.6.7.

Es gibt auch GROSSBUCHSTABEN auf der Tastatur.

Ich denke nicht, das hier irgendjemand allzuviel mit Deiner 
Beschreibung etwas anfangen kann. Wie währe es, wenn Du die 
relevanten Auszüge aus /etc/exports (Server) mitlieferst, 
sowie die genauen Fehler die ausgegeben werden ?

Desweitern solltest Du schreinben, was für Betriebssysteme 
und welcher Versionen auf den jeweiligen Computern laufen. 

Das gleiche gilt auch für die verwendeten NFS-Tools und die 
beiden Kernel-Versionen (vollständig). 

So wie es aussieht, macht der Server nur v2 und der Client v3.

mfg georg

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

nfs-problem geht weiter...

[Michelle Konzack]

Hallo, 

Da mein FileServer (3Ware Raid-5, 3xIBM 120 GByte) von ein paar 
Wochen zu klein wurde, habe ich einen zweiten 3Ware Controller 
mit drei 160 GByte zusätzlich eingebaut. 

Bin mit michelle danach umgezogen und soweit alles gut, mit 
Ausnahme von 'mutt' !

Der neue Plattensatz ist /home1 und /etc/exports angepßt. 
Mounten geht auch einwndfrei. 

'mutt' hat seit dem umzug allerdings Probleme, wenn ich eine 
E-mail editieren will... 
  __
 /
| Warte auf fcntl-Lock... 1 2 3 4
| Konnte temporäre Mailbox nicht erzeugen: keine Berechtigung
 \__

Habe jetzt einfach michelle nochmal auf /home angelegt, 
meine .bashrc und .bash_profile sowie Maildir und ~/.mutt/ 
hineinkopiert, die /etc/passwd angepaßt und nun geht es wieder...

Was kann da sein ?

Der Eintrag für /home1 in der /etc/exports wurde einfach von 
/home kopiert, womit sich in den optionen nichts geändert hat. 

Desweiteren habe ich alle Dateien in /home1/michelle/ gegreped 
und /home/ in /home1/ ausgetauscht (es lebe mozille und openoffice)

Greetings
Michelle

-- 
Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ 


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: nfs-problem geht weiter...

[Timo Eckert]

On Wed, 7 Apr 2004 08:40:34 +0200
Michelle Konzack [EMAIL PROTECTED] wrote:

 Hallo, 

Hallo Michelle,

 'mutt' hat seit dem umzug allerdings Probleme, wenn ich eine 
 E-mail editieren will... 
   __
  /
 | Warte auf fcntl-Lock... 1 2 3 4
 | Konnte temporäre Mailbox nicht erzeugen: keine Berechtigung
  \__
 

Ich würde mal vorschlagen mutt mit strace zu tracen.

strace -o mutt.trace mutt

o.ä.
Dann siehst Du welche Dateien er als letztes versucht zu öffnen zu locken etc.

Sonnige Grüsse
Timo.

[SOLVED] Re: nfs-problem geht weiter...

[Michelle Konzack]

Hallo, 

dachdem ich mit meinem Escalade und den Festplatten auf einen PII 
umgezogen bin, konnte ich meinen selbstkompilierten Kernel nicht 
mehr verwenden, weshalb ich den bf24 als default eingestellt habe.

Ich mounte den nfs-Server mit der option tcp !!!

Das wars !

Im standard bf24 kernel ist diese Option nicht in das 'nfs' und 
'nfsd' kompiliert und hat mir diesen ärger bereitet !

Das entfernen dieser Option aus der fstab hat geholfen. 
Nun heist es wieder Kernel kompilieren.

Die Frage ist nun, warum funktioniert tcp nur mit dem ersten 
nfs-mount /home und nicht mit dem zweiten /home1 ? 

Alle anderen Benutzer, die in /home geblieben sind, haben 
diese Problem nicht. 

Michelle


Am 2004-04-07 08:40:34, schrieb Michelle Konzack:
Hallo, 

Da mein FileServer (3Ware Raid-5, 3xIBM 120 GByte) von ein paar 
Wochen zu klein wurde, habe ich einen zweiten 3Ware Controller 
mit drei 160 GByte zusätzlich eingebaut. 

Bin mit michelle danach umgezogen und soweit alles gut, mit 
Ausnahme von 'mutt' !

Der neue Plattensatz ist /home1 und /etc/exports angepßt. 
Mounten geht auch einwndfrei. 

'mutt' hat seit dem umzug allerdings Probleme, wenn ich eine 
E-mail editieren will... 
  __
 /
| Warte auf fcntl-Lock... 1 2 3 4
| Konnte temporäre Mailbox nicht erzeugen: keine Berechtigung
 \__

Habe jetzt einfach michelle nochmal auf /home angelegt, 
meine .bashrc und .bash_profile sowie Maildir und ~/.mutt/ 
hineinkopiert, die /etc/passwd angepaßt und nun geht es wieder...

Was kann da sein ?

Der Eintrag für /home1 in der /etc/exports wurde einfach von 
/home kopiert, womit sich in den optionen nichts geändert hat. 

Desweiteren habe ich alle Dateien in /home1/michelle/ gegreped 
und /home/ in /home1/ ausgetauscht (es lebe mozille und openoffice)

Greetings
Michelle

-- 
Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ 


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

More info (Was: NFS problem between Solaris Debian)

[Mauricio]

	Here is more info:  the client reports

[EMAIL PROTECTED]nfsstat -rc

Client rpc:
Connection oriented:
calls   badcallsbadxids timeoutsnewcredsbadverfs
6838681 151128  3   297 0   0
timers  cantconnnomem   interrupts
0   680 0   0
Connectionless:
calls   badcallsretrans badxids timeoutsnewcreds
293 1   0   0   0   0
badverfstimers  nomem   cantsend
0   18  0   0
[EMAIL PROTECTED]
timeout  badxids : packets are never making it to the server.  Server too
loaded to reply?
And the server tells me

laurel:/var/local# vmstat 10
procs ---memory-- ---swap-- -io --system-- cpu
 r  b   swpd   free   buff  cache   si   sobibo   incs us sy id wa
 0  0   5608   5580  31092 298428005688521  0  0 99  0
 0  0   5608   5572  31100 29842800 011  12719  0  0 100  0
 0  0   5608   5524  31116 29846000 017  16151  0  0 100  0
 0  0   5608   5524  31116 29846000 0 0  12417  0  0 100  0
 0  0   5608   5524  31116 29846000 0 0  11116  0  0 100  0
 0  0   5608   5520  31120 29846000 016  244   208  0  0 100  0
laurel:/var/local#

From the id column, server cpu has lots of idle time.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nfs-Problem ?

[Michelle Konzack]

Guten Morgen, 

seit gestern habe ich ein misteriöses Problem...

Ich habe meine beiden homes (/home und /home1) seit ewigkeiten über 
über nfs gemounted und nie probleme gehabt. Nun habe ich, wenn ich 
mit mutt arbeite das problem, das ich keine E-Mails mehr editieren 
kann. 

Ich bekomme jedesmal die Fehlermeldung:

  __
 /
| Warte auf fcntl-Lock... 1 2 3 4
| Konnte tempräre Mailbox nicht erzeugen: keine Berechtigung
 \__

Ich verwende maildir und dachte erst, ich habe in meinem Raid-5 array 
keine Inodes mehr... bei 4,4 millionen Messages leicht möglich, nur 
habe ich eben noch 3,8 millionen übrig...

Auch kann ich von anderen programmen einwandfrei in mein Home schreiben
und habe noch 130 GByte frei.

Kennt jemand das problem ?

Oh ja, seit meinem update des X-Window-systems verhält sich mein mozilla 
1.6 bischen eigenartig, sprich, er fängt an, meine SWAP zuzumüllen und 
wemm keine SWAP mehr vorhanden ist, nimmt er den Speicher. 

Ich habe auf der Kiste eine 200 MByte SWAP und 512 MByte SDRAM.
Aber SWAP und SDRAM werden innerhalb einer einzigen sitzung von 3-4 
Stunden dichtgemacht (surfen auf eBay)

Danach verabschiedet sich mozilla ohne Vorwarnung.

Ich dachte erst, das aufgrund des Speichermangels ein problem mit dem 
nfs-common gegeben hat weshalb ich ein

  __
 /
| [EMAIL PROTECTED]:~  /etc/init.d/nfs.common restart
| Stopping NFS common utilities: statd
| Starting NFS common utilities: statd
 \__

was aber auch nichts gebracht hat. 

Also ich will das problem lösen, ohne den rechner neu zu booten...

Nur wie ?

Schönen Tag
Michelle

-- 
Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ 


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: nfs-Problem ?

[Torsten Schneider]

On Thu, Apr 01, 2004 at 10:33:13AM +0200, Michelle Konzack wrote:

 | Warte auf fcntl-Lock... 1 2 3 4
 | Konnte tempräre Mailbox nicht erzeugen: keine Berechtigung

naja, steht doch da, das Locking macht Probleme. Kontrollier mal den
rpc.lockd.


Grüße, Torsten


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: nfs-Problem?

[jan.kesten]

Hallo,

sieht nach einem Probem mit dem locking aus. Welche Kernelversion verwendest Du? Hat 
sich die eventuell auch geaendert? Hatte neulich aehnliche Probleme... 

Verwendest Du den Kernel NFS oder User-Space NFS Daemon?

Cheers,
Jan



-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: nfs-Problem?

[Michelle Konzack]

Am 2004-04-01 11:04:15, schrieb [EMAIL PROTECTED]:
Hallo,

sieht nach einem Probem mit dem locking aus. Welche Kernelversion verwendest Du? Hat 
sich die eventuell auch geaendert? Hatte neulich aehnliche Probleme... 

Verwendest Du den Kernel NFS oder User-Space NFS Daemon?

Mein FileServer verwendet den bf24. 
Desweiteren habe ich den nfs-user-server

Beides läuft aber seit leztem Jahr unverändert, wenn man davon 
absieht, das ich vor zwei Wochen einen zweiten Escalade mit drei 
160 GByte Platten hinzugefügt habe.

Meine Workstation lief auf einem 2.4.24er und nachdem ich nun eine 
andere CPU habe bootete ich mit bf24 vor zwei Wochen...

Der Fehler ist ja erst gestern aufgetaucht. Von einer Minute auf die 
andere. Ich konnte noch ein paar HTML-Mails editieren und paar 
Minuten später war es nicht mehr möglich.

Denke, das ich vieleicht doch die Kiste neu booten muß.

Ach ja, jedesmal, wenn ich eine E-mail schreibe und dann abspeichere, 
verlasse ich ganz normal den Editor und bin wieder zurück in mutt, 
nur sagt er mir jedesmal das die Codierung geändert wurde und ob ich 
die neue verwenden will ???

Cheers,
Jan

Greetings
Michelle

-- 
Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ 


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

NFS problem between Solaris Debian

[Mauricio]

NFS problem.  Server is a debian Sarge/testing box (kernel 
2.4.25-1-386).  Client is a solaris 8 box.  This afternoon I started 
to see the following messages in the debian box's
/var/log/kern.log:

Apr  1 15:40:00 laurel kernel: rpc-srv/tcp: nfsd: sent only -32 bytes 
of 8324 - shutting down socket

What is going on here?

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Andre Kalus]

On Mon, 27 Oct 2003 16:01:06 -0500, Vivek Kumar wrote:

 Hi,
 
 I am trying to mount a directory as nfs filesystem from other machine. I
 am getting RPC error on other machine and it says  (Host linux box)
 is not responding. Though I can ping to the linux box from there and
 also I can telnet ot it.
 What is that I am missing. Any suggestion.
 
 Thanks

These services are needed to be run on the server side:
- NFS server
- Portmap

Check if one of them is started via Inetd (etc/inetd.conf): if one is then
you also need to start inetd.

Check the log of your server if it is receiving any requests.

Greetings
Andre


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Wilko Fokken]

BTW, is there still a way to mount a windows dirtree via nfs ?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nfs problem

[Vivek Kumar]

Hi,

I am trying to mount a directory as nfs filesystem from other machine. I
am getting RPC error on other machine and it says  (Host linux box)
is not responding. Though I can ping to the linux box from there and
also I can telnet ot it.
What is that I am missing. Any suggestion.

Thanks
-- 
Vivek


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Kjetil Kjernsmo]

On Monday 27 October 2003 22:01, Vivek Kumar wrote:
 I am trying to mount a directory as nfs filesystem from other
 machine. I am getting RPC error on other machine and it says 
 (Host linux box) is not responding. Though I can ping to the linux
 box from there and also I can telnet ot it.

What ports are open? Perhaps you've firewalled off some of the ports you 
need. nmap it, perhaps?

Best,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

A little more on my nfs problem...

[Neal Lippman]

Also, some more stuff I've been noticing:

1) My understanding was that /var/lib/nfs/xtab was the file actually
consulted by mountd to respond to an nfs mount request. Interestingly,
that file only contains the info on /home, but not on the /shared
export, even though /etc/exports includes both.

The same directory has a file called etab, and that file does contain
both exports.

Issuing exportfs -a -v prints out two lines, indicating both exports are
being processed, but xtab doesn't change. I don't understand this.
exportfs -r gives the same behavoir.

I tried exporting another directory (/tmp) by adding it to /etc/exports
and reissuing exportfs -a - the new export got added to etab but not
xtab, and in any case I could not mount the new share either - same
connection refused error from the workstation.

2) I thought maybe the problem was that the /shared mount point is
Reiserfs, thinking (without good reason) that maybe there is a problem
with nfs exporting reiser filesystems, but the /tmp export I
experimented with is ext2 (as is /home, the export that seems to work,
at least for now).

I suspect there is something wrong with mountd, and that it died after
letting me mount the one export that works, but I cannot figure out what
it is. There are no error messages in syslog to help me.

nl




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: kleines nfs problem

[Christian Schmidt]

Alois Stöckl schrieb/wrote:

 hab ein kleines Problem mit nfs.
 Auf meinem Mailrechner der auch als winzling von Server dient gibt es ein 
 Verzeichnis das ich über nfs zur verfügung stelle. Diese Hälfte der NFS 
 Verbindung funktioniert auch. Jetzt habe ich mal zum testen die 3.2 er 
 knoppix auf einem meiner Rechner installiert. Die installation läuft auch, 
 soweit ich sie testen konnte ganz pasabel, nur kann ich das exportierte 
 Verzeichnis dort nicht mounten.
 (boote ich Knoppix von CD und erstelle den Mountpoint tut es) 
 Das modul nfs habe ich geladen. Wo könnte der Hund begraben sein ???
 (die IP Adressen stimmen)

Aeussert sich Dein kann nicht mounten auch in Form irgendeiner
Fehlermeldung?

Gruss,
Christian

-- 
Christian Schmidt | Germany 
PGP Key ID: 0x28266F2C
No HTML Mails, please!


pgp0.pgp
Description: PGP signature

kleines nfs problem

[Alois Stöckl]

Hallo liebe Listenleser,

hab ein kleines Problem mit nfs.
Auf meinem Mailrechner der auch als winzling von Server dient gibt es ein 
Verzeichnis das ich über nfs zur verfügung stelle. Diese Hälfte der NFS 
Verbindung funktioniert auch. Jetzt habe ich mal zum testen die 3.2 er 
knoppix auf einem meiner Rechner installiert. Die installation läuft auch, 
soweit ich sie testen konnte ganz pasabel, nur kann ich das exportierte 
Verzeichnis dort nicht mounten.
(boote ich Knoppix von CD und erstelle den Mountpoint tut es) 
Das modul nfs habe ich geladen. Wo könnte der Hund begraben sein ???
(die IP Adressen stimmen)

Mit Dank im voraus

Alois


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: nfs problem

[Mark C]

On Wed, 2003-07-30 at 05:31, gerard wrote:
 Everything was working fine with my nfs, rebooted, and now when I try to
 mount an nfs drive this is the error I get mount: RPC: Unable to
 receive; errno = Connection refused. Any ideas? I havent changed
 anything either, thats why I find it strange.

try running:
 
/sbin/portmap (needed)
/sbin/rpc.statd 
/sbin/rpc.lockd

If you are going to run nfs, then you will need these running, also make
sure that /etc/init.d/nfs-common is running on startup.

Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Dave Carrigan]

On Wed, Jul 30, 2003 at 12:31:13AM -0400, gerard wrote:
 Everything was working fine with my nfs, rebooted, and now when I try to
 mount an nfs drive this is the error I get mount: RPC: Unable to
 receive; errno = Connection refused. Any ideas? I havent changed
 anything either, thats why I find it strange.

There have been some bugs in recent versions of nfs-kernel-server and/or
nfs-common. Make sure you're running the most recent ones or else
downgrade to 1.0.3-1.

-- 
Dave Carrigan
Seattle, WA, USA
[EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680
UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Ron Johnson]

On Wed, 2003-07-30 at 07:51, Dave Carrigan wrote:
 On Wed, Jul 30, 2003 at 12:31:13AM -0400, gerard wrote:
  Everything was working fine with my nfs, rebooted, and now when I try to
  mount an nfs drive this is the error I get mount: RPC: Unable to
  receive; errno = Connection refused. Any ideas? I havent changed
  anything either, thats why I find it strange.
 
 There have been some bugs in recent versions of nfs-kernel-server and/or
 nfs-common. Make sure you're running the most recent ones or else
 downgrade to 1.0.3-1.

The same thing has happened to me.

On the client:

# ps aux |grep portmap
daemon  340  0.0  0.0  1316  396 ? SJul29   0:00 /sbin/portmap

#  ps aux |grep statd
root   2477  0.0  0.1  1372  680 ? S10:19   0:00 /sbin/rpc.statd

# ps aux |grep lockd
root   2462  0.0  0.0 00 ? W   10:19   0:00 [lockd]

# dpkg -l | grep nfs
ii  nfs-common 1.0.3-2 NFS support files common to client and serve
ii  nfs-kernel-ser 1.0.3-2 Kernel NFS server support

# mount /nfs/music
mount: RPC: Unable to receive; errno = Connection refused

On the server:

$ ps aux |grep portmap
daemon  272  0.0  0.0  1320  468 ? S  Jun25   0:00 [portmap]

[EMAIL PROTECTED]:~$ ps aux |grep statd
root854  0.0  0.0  1372  680 ? S  Jul27   0:00 /sbin/rpc.statd

[EMAIL PROTECTED]:~$ ps aux |grep lockd
root925  0.0  0.0 00 ? SW Jul27   0:00 [lockd]

$ dpkg -l | grep nfs
ii  nfs-common 1.0.3-2 NFS support files common to client and serve
ii  nfs-kernel-ser 1.0.3-2 Kernel NFS server support

-- 
+-+
| Ron Johnson, Jr.Home: [EMAIL PROTECTED] |
| Jefferson, LA  USA  |
| |
| I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!|
|unknown  |
+-+



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Dave Carrigan]

On Wed, Jul 30, 2003 at 10:28:29AM -0500, Ron Johnson wrote:
 On Wed, 2003-07-30 at 07:51, Dave Carrigan wrote:

  Make sure you're running the most recent ones or else
  downgrade to 1.0.3-1.

 # dpkg -l | grep nfs
 ii  nfs-common 1.0.3-2 NFS support files common to client and serve
 ii  nfs-kernel-ser 1.0.3-2 Kernel NFS server support
 ^^^

You have to downgrade to 1.0.3-1.

-- 
Dave Carrigan
Seattle, WA, USA
[EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680
UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Ron Johnson]

On Wed, 2003-07-30 at 12:08, Dave Carrigan wrote:
 On Wed, Jul 30, 2003 at 10:28:29AM -0500, Ron Johnson wrote:
  On Wed, 2003-07-30 at 07:51, Dave Carrigan wrote:
 
   Make sure you're running the most recent ones or else
   downgrade to 1.0.3-1.
 
  # dpkg -l | grep nfs
  ii  nfs-common 1.0.3-2 NFS support files common to client and serve
  ii  nfs-kernel-ser 1.0.3-2 Kernel NFS server support
  ^^^
 
 You have to downgrade to 1.0.3-1.

Those pesky digits!

Thanks.  Does sid's 1.0.5-1 work?

-- 
+-+
| Ron Johnson, Jr.Home: [EMAIL PROTECTED] |
| Jefferson, LA  USA  |
| |
| I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!|
|unknown  |
+-+



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nfs problem

[Dave Carrigan]

On Wed, Jul 30, 2003 at 06:39:52PM -0500, Ron Johnson wrote:

 Thanks.  Does sid's 1.0.5-1 work?

Yes, seems to be working for me.

-- 
Dave Carrigan
Seattle, WA, USA
[EMAIL PROTECTED] | http://www.rudedog.org/ | ICQ:161669680
UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-C++-DNS-PalmOS-PostgreSQL-MySQL

Dave is currently listening to Dream Academy - The Edge Of Forever (The Dream Academy)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nfs problem

[gerard]

Everything was working fine with my nfs, rebooted, and now when I try to
mount an nfs drive this is the error I get mount: RPC: Unable to
receive; errno = Connection refused. Any ideas? I havent changed
anything either, thats why I find it strange.

~gerard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

NFS Problem

[Bart Lenoir]

Hi,

I'm running an NFS server on Red Hat.
Connected to the Red Hat I have a Debian 
which I want to use as an NFS client.
Ping, Ftp, Telnet, ... all seems fine.
Mount and Umount is working well, however
I don't have access to the selected directory.
Permission denied. The only way I can have
access to this directory is to set Red Hat 
/etc/exports to (rw,sync,no_root_squash).
Logging in as root on Debian I'm having access 
but that is not what I want. Why do I get 
Permission refused as regular user?

On another Red Hat I do have access as regular user.

rpcinfo -p on Debian

# rpcinfo -p
   program vers proto   port
102   tcp111  portmapper
102   udp111  portmapper
1000241   udp867  status
1000241   tcp870  status
3910021   tcp  32768  sgi_fam
3910022   tcp  32768  sgi_fam
1000211   udp  32769  nlockmgr
1000213   udp  32769  nlockmgr
1000214   udp  32769  nlockmgr

Thanks,
Bart


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: NFS Problem

[Zhao You Bing]

Bart Lenoir wrote:
Hi,

I'm running an NFS server on Red Hat.
Connected to the Red Hat I have a Debian 
which I want to use as an NFS client.
Ping, Ftp, Telnet, ... all seems fine.
Mount and Umount is working well, however
I don't have access to the selected directory.
Permission denied. The only way I can have
access to this directory is to set Red Hat 
/etc/exports to (rw,sync,no_root_squash).
Logging in as root on Debian I'm having access 
but that is not what I want. Why do I get 
Permission refused as regular user?

On another Red Hat I do have access as regular user.

rpcinfo -p on Debian

# rpcinfo -p
   program vers proto   port
102   tcp111  portmapper
102   udp111  portmapper
1000241   udp867  status
1000241   tcp870  status
3910021   tcp  32768  sgi_fam
3910022   tcp  32768  sgi_fam
1000211   udp  32769  nlockmgr
1000213   udp  32769  nlockmgr
1000214   udp  32769  nlockmgr
Thanks,
Bart

I think nfs requires u have same user id on both the system if u want to 
have full rights (very dangerous I think)

so u need to change /etc/passwd to have same user id. Redhat starts user 
id from 500 while Debian starts from 1000, I did manually changed the 
user id to have nfs access.

--
Zhao YouBing, Ph.D student
State Key Lab of CADCG,Zhejiang University,
Hangzhou, 310027, P.R.China
Tel  : 0571-87951045(O), 87933444(H)
Email: [EMAIL PROTECTED]
MSN  : [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: tar/NFS problem

[Florian Ernst]

Hello Piers!

Piers Kittel wrote:
 [...Backup...]
 00 4 * * 0 root rm -f /home/desirebackup/home_backup.tar; tar cf
 /home/desirebackup/home_backup.tar /home/desire/piers

Hmm, you completely delete your older backup, and then you try to get
a new one?
What do you think might happen once an error occurs directly after
deleting the old backup? You will end up with _no_ backup at all.

Better put it in this order: create a new backup, verify its
integrity, maybe delete the old backup thereafter.


CU,
Flo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: tar/NFS problem

[Paladin]

On Wed, 16 Jul 2003 11:03:07 +0200
Florian Ernst [EMAIL PROTECTED] wrote:

  Hmm, you completely delete your older backup, and then you try to
  get a new one?
  What do you think might happen once an error occurs directly
  after deleting the old backup? You will end up with _no_ backup
  at all.
 
  Better put it in this order: create a new backup, verify its
  integrity, maybe delete the old backup thereafter.

Why not just do an update on the tar file?

---
Paladin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: tar/NFS problem

[Florian Ernst]

Hello Paladin!

Paladin wrote:
 On Wed, 16 Jul 2003 11:03:07 +0200
 Florian Ernst [EMAIL PROTECTED] wrote:
 
  Hmm, you completely delete your older backup, and then you try to
  get a new one?
  What do you think might happen once an error occurs directly
  after deleting the old backup? You will end up with _no_ backup
  at all.
 
  Better put it in this order: create a new backup, verify its
  integrity, maybe delete the old backup thereafter.
 
 Why not just do an update on the tar file?

That depends on the preferred backup scheme.

I personally prefer to keep old backups completely untouched /
unchanged in order to eliminate the slightest chance of corruption
during such a change.
Certainly this causes a need for more backup space, but all the time I
have a working backup no matter what happens during the latest
backup.

Just imagine the tar file gets corrupt during the update, you will end
up with no backup at all.
Imagine the corruption (or simply bad luck) spreads over to the files
you originally wanted to backup, you will end up with _nothing_ at
all.

I hope to have clarified my point in this,
CU,
Flo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: tar/NFS problem

[Piers Kittel]

Florian,

You are completely correct, and I totally agree, but the issue here is 
that the hard drive in Destiny is 12Gb, and the backup is around 6GB and 
so there isn't room for 2 backups.

Interestingly, when I tried to tar the files on the main PC (Desire) and 
then copy it over via NFS, I always find the receving PC thinks the file 
is far smaller than it actually is - Destiny thinks the .tar file stored 
on Desire is 1Gb, but in actuality its 5Gb.

Strange.

Cheers - Piers

Florian Ernst wrote:
 Hello Paladin!

 Paladin wrote:

On Wed, 16 Jul 2003 11:03:07 +0200
Florian Ernst [EMAIL PROTECTED] wrote:


 Hmm, you completely delete your older backup, and then you try to
 get a new one?
 What do you think might happen once an error occurs directly
 after deleting the old backup? You will end up with _no_ backup
 at all.

 Better put it in this order: create a new backup, verify its
 integrity, maybe delete the old backup thereafter.

Why not just do an update on the tar file?


 That depends on the preferred backup scheme.

 I personally prefer to keep old backups completely untouched /
 unchanged in order to eliminate the slightest chance of corruption
 during such a change.
 Certainly this causes a need for more backup space, but all the time I
 have a working backup no matter what happens during the latest
 backup.

 Just imagine the tar file gets corrupt during the update, you will end
 up with no backup at all.
 Imagine the corruption (or simply bad luck) spreads over to the files
 you originally wanted to backup, you will end up with _nothing_ at
 all.

 I hope to have clarified my point in this,
 CU,
 Flo


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: tar/NFS problem

[Piers Kittel]

Great!  Seems to be working

Cheers!

Piers

Michael Heironimus wrote:
 On Wed, Jul 16, 2003 at 01:24:45AM +0100, Piers Kittel wrote:

Bascially, I've got 2 computers, one which is my main PC (named desire),
and the other is a server (named destiny).  I'd like the server to
backup the /home/piers directory from the main PC.  The server is
accessing the main PC by NFS and desire:/home is moutned on
destiny:/home/desire.  I've put in the following line in the crontab
file on destiny:

00 4 * * 0 root rm -f /home/desirebackup/home_backup.tar; tar cf
/home/desirebackup/home_backup.tar /home/desire/piers

but when I tested out the tar cf /home/desirebackup/home_backup.tar
/home/desire/piers I get a lot of Permissions denied errors although
some files are read OK. (An example is tar: /home/desire/piers/.mcoprc:
Read error at byte 0, reading 31 byes: Permission denied)


 It looks like you're using root to run your backup. Normally root is
 remapped to nobody (root squashing) on NFS mounts for security
 reasons, so root won't have permission to read files that aren't
 world-readable. In the /etc/exports file on the server you can add the
 no_root_squash option to allow root access on an exported filesystem.
 See the man page on exports for details.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: tar/NFS problem

[Piers Kittel]

Furthering the subject...

Is it possible to get the crontab to email me each time the job 
succeeds/fails or is it better to write a shell script and get crontab 
to execute the script?

Cheers - Piers

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: tar/NFS problem

[Bijan Soleymani]

--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 16, 2003 at 06:47:30PM +0100, Piers Kittel wrote:
 Furthering the subject...
=20
 Is it possible to get the crontab to email me each time the job=20
 succeeds/fails or is it better to write a shell script and get crontab=20
 to execute the script?

Cron usually mails me any errors. I usually end up doing:
script  /dev/null

because sometimes it overloads me with mail.

Bijan


--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/FZx6Uof+95vTyAwRAoaMAJwPVuofSW6i8SmoqmNe2U3r4larKwCdGdBQ
j6p5b8On9zZktoDNRx3SJb4=
=PmXr
-END PGP SIGNATURE-

--uAKRQypu60I7Lcqm--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]