[mythtv-users] Shared filesystem that looks different to different machines

jedi jedi at mishnet.org
Wed Jun 4 17:52:58 UTC 2014


On Wed, Jun 04, 2014 at 07:45:14PM +0200, Hika van den Hoven wrote:
> Hoi Hika,
> 
> Wednesday, June 4, 2014, 7:39:47 PM, you wrote:
> 
> > Hoi John,
> 
> > Wednesday, June 4, 2014, 6:26:17 PM, you wrote:
> 
> >> On 6/4/2014 8:20 AM, Raymond Wagner wrote:
> >>> On 6/4/2014 10:53 AM, Joseph Fry wrote:
> >>>> I don't believe that NFS would have any issue with nesting a mount 
> >>>> inside another mount like this, after all the OS just treats it as 
> >>>> another filesystem and every linux system I have ever seen does this 
> >>>> (/dev, /proc, etc).
> >>>
> >>> NFS can have issues if you mount one NFS volume within another NFS 
> >>> volume.  If access to the lower volume is ever anything but 100% 
> >>> stable, and the mount point for the upper volume is lost, bad things 
> >>> happen.  It's the same reason why you never use an NFS share for swap 
> >>> space.
> 
> >> Mounting one NFS filesystem on another NFS filesystem has been commonly
> >> used from the beginning of NFS: diskless systems did this all the time.
> 
> > True, but if the bottom nfs filesystem gets dirty, which is very
> > common if it is accessed by more then one client, you cannot access it
> > anymore nor can you remount. You have to reboot.
> 
> You can however large prevent this by exporting the bottom share
> read-only!

    ...sounds familiar. A lot of the stuff related to MythTV isn't stuff
you would want to be mounted read/write on most (if not all) of your boxes
anyways.



More information about the mythtv-users mailing list