CacheFS Issues

From: Jeff McCombs (jeffm_at_nicusa.com)
Date: 03/15/04

  • Next message: Russell, Shawn (GE Consumer & Industrial): "format, type, auto-configure fails"
    To: <sunmanagers@sunmanagers.org>
    Date: Mon, 15 Mar 2004 14:30:45 -0600
    
    

    Gurus,

            I'm hoping that someone can help me out. I've been beating my head
    against this for a few days now and can't seem to come up with a reason as
    to why this is happening.

            We've got two 240s running VxFS/VxVM/HA and acting as a
    primary/secondary NFS server, with an A5200 as the storage unit.

            I've got about 20 some odd systems ranging from V100's to V210s that
    will be mounting the NFS "cluster" (I use that term loosely here) as
    application and web services systems in r/o mode and I thought that this
    would be the perfect situation for cacheFS. First because I can foresee the
    need in the future to scale, and I might as well get it setup now and
    secondly because I like the added piece of mind that the cachefs disconnect
    (if used with cachefspack) feature gives me.

            My problem is that I can't get cacheFS to work properly on system
    reboots, even though the proper entries are in /etc/vfstab.

    Vfstab reads as follows (all on one line obviously):
    nfs-web:/export/home - /home cachefs 7 yes
    nosuid,backfstype=nfs,cachedir=/usr/cache,local-access

            What happens is that the system comes up and the share gets mounted,
    but the cache-mount point changes every time there's a reboot:

    jeffm@web-1(pts/1):~> df -h /portal
    Filesystem size used avail capacity Mounted on
    /usr/cache/.cfs_mnt_points/nfs-web:_export_prod_web_portal_3
                           339G 101M 318G 1% /portal

            That /usr/cache/.cfs_mnt_points/nfs-web:/_export_prod_web_portal_3
    line will change to foo_bar_portal_4 the next time the system boots.

            Now I've run cachefs in the past, albeit on older versions of
    Solaris (2.5, 2.6) and never noticed this problem before. But because I
    didn't notice it, doesn't mean that it wasn't happening. So maybe it's
    normal(?)

            Another fun thing I've noticed is that cachefsd is not being
    started. One of the reasons for me to move to cacheFS is that I like the
    disconnect feature that cachefs provides. However, for that to work I need
    cachefsd.

            If I unmount / remount the share, via "umount /portal ; mount
    /portal" cachefsd starts right up _AND_ my cache mount point stays the same.
    That number at the tail end doesn't increment.

            According to docs.sun.com, cachefsd is supposed to be started
    automatically from inetd when a mount_cachefs is invoked... isn't that what
    the system does when it's mounting vfstab entries with the fstype of
    cachefs?

            I checked to make sure that rpc and the cachefs entries in
    inetd.conf existed, and rpcbind is running, and everything seems to be in
    working order. I also double checked to make sure that I didn't miss
    re-enabling the nfs.client and cacheFS rc2.d scripts after JASS had disabled
    them (they were fine).

            Anyone seen this before? Solaris 9 12/03 release. Latest (as of
    3/1/04) recommended patch set installed. Highly customized package set
    installed (SUNWreq, plus a few minor additions - web servers don't need
    SUNWall!).

    -Jeff

    "If you try to fail, and you succeed, what did you just do?"
    -----------------------------------------------------------------------
      Jeff McCombs (jeffm@nicusa.com) NIC, Inc.
      Systems Administrator 10540 S. Ridgeview Rd.
      (913) 754-7027 - Office Olathe, KS 66061
      (317) 523-9751 - Cell (913) 498-3472 - Fax
                    "NIC, Inc. - The people behind eGovernment"
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: Russell, Shawn (GE Consumer & Industrial): "format, type, auto-configure fails"