Doug Hughes wrote:
> Jonathan B Bayer wrote:
[snip]
>> Each virtual system will have a relatively small partition to boot
>> from. The data partition (/var) will be accessed via either NFS or
>> CIFS. The exported filesystems will be on the CentOS server, and
>> exported to each individual virtual system. Each virtual system will
>> access a different exported directory
[snip]
> To me, it seems like far too little information to make any solid
> recommendations. You don't say who the clients are, or what they are
> doing, or how many of them with what sized files? Is it I/O bound or
> some other characteristic? Is it bandwidth or latency? throughput or
> IOPS? What are your uptime requirements and SLAs? So many questions..
Actually for the use he gave, there is enough information.
I would never use /var as CIFS in any production use.
As mentioned previously (someone else's reply), the authentication
schemes do not match. If you mount /var via CIFS, you authenticate
as a single user. That single user is what will be accessing ALL files
in /var. So, if you authenticate the mount as "Joe", then root will
not have root access to /var, just "Joe" access. If you authenticate
as "root", then all users of the client system will have root access
to /var.
For NFS, you mount a share as /var, then every user on the client can
access /var as themselves. Though for NFS and shared mounts (which the
OP is not doing,) the /etc/passwd and /etc/group files need to be
synchronized between all clients.
--
END OF LINE
--MCP
_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
