Simon Gao wrote:
>
> I am using NFS v3. I don't believe I am the only one or first one running
> into this problem. I would like to know how others deal with such problem.
> Using OpenSolaris is not an option in our production environment.
>
> Without being able to use sub file systems easily,
On Wed, 21 Nov 2007 22:36:18 +0100, Simon Gao wrote:
>> Simon Gao wrote:
>> > Here is one issue I am running into when setting up
>> a new NFS server to share several zfs file systems.
>> >
>> > I created following zfs file system from a zfs pool
>> called bigpool. The bigpool is the top level fi
Assuming that your client supports executable automount maps,
then this thread maybe relevant.
http://www.opensolaris.org/jive/thread.jspa?messageID=55941
On Nov 21, 2007, at 3:36 PM, Simon Gao wrote:
>
> I am using NFS v3. I don't believe I am the only one or first one
> running into this p
On Nov 21, 2007, at 3:03 PM, Tom Haynes wrote:
> Robert Gordon wrote:
>> It sounds like the Linux client did not perform a 'mirror' mount,
>> thus you
>> actually see the 'pseudo namespace' directory.
>>
>
> If it is NFSv4, I've seen modern Linux clients do the equivalent of a
> mirror mount.
>
>
Robert Gordon wrote:
> It sounds like the Linux client did not perform a 'mirror' mount,
> thus you
> actually see the 'pseudo namespace' directory.
>
If it is NFSv4, I've seen modern Linux clients do the equivalent of a
mirror mount.
If it is NFSv3, then he does need an automounter.
> Two
Simon Gao wrote:
> Here is one issue I am running into when setting up a new NFS server to share
> several zfs file systems.
>
> I created following zfs file system from a zfs pool called bigpool. The
> bigpool is the top level file system and mounted as /export/bigpool.
>
> file system
It sounds like the Linux client did not perform a 'mirror' mount,
thus you
actually see the 'pseudo namespace' directory.
Two options to allow seamless mounting:
(a) Use openSolaris clients that support 'mirror mounts'
(b) Use automounter to perform the mounts needed.
Robert.
On Nov 21, 200
On 11/21/07 13:54, Simon Gao wrote:
> Using autofs to mount each sub zfs file system will be a lot of hassle. Every
> time creating a new zfs file system, I will have to update automount map and
> push it out and reload on every client.
>
>
You are correct. That's why the NFS guys just integra
> Simon Gao wrote:
> > Here is one issue I am running into when setting up
> a new NFS server to share several zfs file systems.
> >
> > I created following zfs file system from a zfs pool
> called bigpool. The bigpool is the top level file
> system and mounted as /export/bigpool.
> >
> > file syst
Using autofs to mount each sub zfs file system will be a lot of hassle. Every
time creating a new zfs file system, I will have to update automount map and
push it out and reload on every client.
Multiple zfs file systems are really nice, but here is a big gotcha. It's not
practical to manage th
Here is one issue I am running into when setting up a new NFS server to share
several zfs file systems.
I created following zfs file system from a zfs pool called bigpool. The bigpool
is the top level file system and mounted as /export/bigpool.
file system mount point
bigpool
11 matches
Mail list logo
