Harry Putnam wrote:
Robert Thurlow writes:
This makes a lot more sense. NFSv4 should have worked for
you if you had the client and server both set to the same
NFSv4 domain - if you care to work on this, we can.
Thanks for the offer. Is there something NFSv4 offers that would make
it wort
Matthias Pfützner
writes:
> Hey, Harry, no problem! Sometimes we all can't see the forest for the
> trees... We all assumed, it must have been something like that.
>
> Glad it worked out finally!
You put quite a bit into it, thanks for you patience and time.
Robert Thurlow writes:
> Harry Putnam wrote:
>
>> Man, I'm really sorry to the list for all my huffing and puffing when
>> I'm pretty sure I had been claiming I had the right settings in
>> /etc/default/nfs (but didn't).
>
> This makes a lot more sense. NFSv4 should have worked for
> you if you
Harry Putnam wrote:
Man, I'm really sorry to the list for all my huffing and puffing when
I'm pretty sure I had been claiming I had the right settings in
/etc/default/nfs (but didn't).
This makes a lot more sense. NFSv4 should have worked for
you if you had the client and server both set to t
Hey, Harry, no problem! Sometimes we all can't see the forest for the
trees... We all assumed, it must have been something like that.
Glad it worked out finally!
Matthias
You (Harry Putnam) wrote:
> Harry Putnam writes:
>
> > That info from your linux client `mount' cmd may tell whats wro
Harry Putnam writes:
> That info from your linux client `mount' cmd may tell whats wrong
> here. Mine has one extra item in there:
>
> OSOL_SERVER:/pub on /pub type
> nfs (rw,users,addr=192.168.0.29,vers=4,clientaddr=192.168.0.2)
>
> Notice the `vers=4' so apparently my linux client is taki
Chris writes:
> Hi Harry, I get files created with UID & GID set by client. See
> below (some names have been altered to protect the innocent, any
> inconsistencies are due to that editing)
[...]
Thanks... nothing like some actual data to see how it ends up.
So something is definitely going a
Hi Harry, I get files created with UID & GID set by client. See below (some
names have been altered to protect the innocent, any inconsistencies are due to
that editing)
from mount list:
192.168.0.110:/darkstar/nebulae on /home/chris/osolnfsmount type nfs
(rw,nolock,addr=192.168.0.110)
ch...@
You (Harry Putnam) wrote:
> Matthias Pfützner
> writes:
> > So, if user "willi" on the Linux client hat UID 4711, then on the SERVER you
> > should see "4711" as the owner of a file, that had been created by "willi"
> > on
> > a filesystems that had been mounted from the server. The server does n
Edward,
You (Edward Ned Harvey) wrote:
> > Do you have any linux clients to osol nfs server?
> >
> > If not Matthias, then is there anyone else here who has an osol NFS
> > server with a linux client, where you can show a simple `ls -l' (on
> > the client) in a directory created on the mounted nf
>I've had bad experience setting NFS mounts in /etc/fstab. The problem is:
>If the filesystem can't mount for any reason, then the machine doesn't come
>up. Unless you set it as a "soft" mount, in which case, the slightest
>little network glitch causes clients to lose their minds.
There is als
Edward Ned Harvey
writes:
>> Do you have any linux clients to osol nfs server?
>>
>> If not Matthias, then is there anyone else here who has an osol NFS
>> server with a linux client, where you can show a simple `ls -l' (on
>> the client) in a directory created on the mounted nfs share, by a
>> l
> Do you have any linux clients to osol nfs server?
>
> If not Matthias, then is there anyone else here who has an osol NFS
> server with a linux client, where you can show a simple `ls -l' (on
> the client) in a directory created on the mounted nfs share, by a
> linux user.
I still think my orig
> The Linux host needs to be able to MOUNT the NFS-exported files.
>
> The /etc/auto.master file is using a later "extension" to the NFS
> system, name
> "automount". This only mounts directories, when they are accessed,
> therefore
> "auto-mount".
>
> You could also add the to-be-mounted diretor
Matthias Pfützner
writes:
> So, if user "willi" on the Linux client hat UID 4711, then on the SERVER you
> should see "4711" as the owner of a file, that had been created by "willi" on
> a filesystems that had been mounted from the server. The server does not need
> to know, that 4711 is "willi",
You (Harry Putnam) wrote:
> Matthias Pfützner
> writes:
>
> > Harry,
> >
> > all very bizarre... ;-)
>
> Probably do to ill informed bumbling on my part.
>
> [...]
>
> >> > What's the output of:
> >> >
> >> > ls -ld /export/home/reader
> >> >
> >> > Does that resolve and list the user
Matthias Pfützner
writes:
> Harry,
>
> all very bizarre... ;-)
Probably do to ill informed bumbling on my part.
[...]
>> > What's the output of:
>> >
>> > ls -ld /export/home/reader
>> >
>> > Does that resolve and list the user-name and group-name?
>>
>> yes, well no.
>>
>> I've f
Harry,
all very bizarre... ;-)
You (Harry Putnam) wrote:
> Matthias Pfützner
> writes:
>
> > Harry,
> >
> > sorry for my first answer, now that you rephrased some of the
> > original post, I now remember, what your initial problam really
> > was... More inline below...
>
> It may not have been
Matthias Pfützner
writes:
> Harry,
>
> sorry for my first answer, now that you rephrased some of the
> original post, I now remember, what your initial problam really
> was... More inline below...
It may not have been or still may not be much of a clear exposition on
my part either...
[...]
>
Mike Gerdts writes:
>>
>> Any files/directories create by the linux user end up with
>> nobody:nobody uid:gid and any attempt to change that from the client
>> host fails, even if done as root.
>
> It looks to me like you are using NFSv4 and the NFS mapping domains do
> not match. See /etc/de
On Mon, Mar 8, 2010 at 10:54 PM, Harry Putnam wrote:
> summary:
>
> A zfs fs set with smb and nfs on, and set chmod g-s (set-gid) with
> a local users uid:gid is being mounted by a remote linux host (and
> windows hosts, but not discussing that here).
>
> The remote user is the same as the loc
Harry,
sorry for my first answer, now that you rephrased some of the original post, I
now remember, what your initial problam really was... More inline below...
You (Harry Putnam) wrote:
> And made these settings:
[...]
> zfs get sharenfs z3/projects
> NAME PROPERTY VALUE SOURC
Matthias Pfützner
writes:
[...]
> You need TWO things:
>
> You need to START the NFS server:
>
> svcadm enable svc:/network/nfs/server:default
>
> and then you need to SHARE some directories. If these are located on
> a ZFS pool, you can easily share that zpool by:
>
> zfs set sharenfs=
You (Harry Putnam) wrote:
> Edward Ned Harvey
> writes:
> > I don't know if there is something deeper going on here, I'll just start by
> > saying I'm doing the same thing (but the server is solaris) and I don't have
> > any problems. This has been in production for quite some time, and used
> >
Edward Ned Harvey
writes:
> I don't know if there is something deeper going on here, I'll just start by
> saying I'm doing the same thing (but the server is solaris) and I don't have
> any problems. This has been in production for quite some time, and used
> heavily by many users and various nfs
> A zfs fs set with smb and nfs on, and set chmod g-s (set-gid) with
> a local users uid:gid is being mounted by a remote linux host (and
> windows hosts, but not discussing that here).
>
> The remote user is the same as the local user in both numeric UID
> and numeric GID
>
> The zfs
summary:
A zfs fs set with smb and nfs on, and set chmod g-s (set-gid) with
a local users uid:gid is being mounted by a remote linux host (and
windows hosts, but not discussing that here).
The remote user is the same as the local user in both numeric UID
and numeric GID
The zfs nfs
27 matches
Mail list logo
