Volker A. Brandt wrote: > Hello Kyle! > > > >> All of these mounts are failing at bootup with messages about >> non-existent mountpoints. My guess is that it's because when /etc/vfstab >> is running, the ZFS '/export/OSImages' isn't mounted yet? >> > > Yes, that is absolutely correct. For details, look at the start method > of svc:/system/filesystem/local:default, which lives in the script > /lib/svc/method/fs-local. There you can see that ZFS is processed > after the vfstab. > > Ok. So my theory was right. :) >> Any ideas? >> > > The only way I could find was to set the mountpoint of the file system > to legacy, and add it to /etc/vfstab. Here's an example: > > I tried this last night also, after sending the message and I made it work. Seems clunky though.
I wonder if there is a technical reason why it has to be done in this order? More importantly, I wonder if ZFS Boot will re-order this since the other FS's will all be ZFS. (Actually I wonder what will be left in /etc/vfstab?) > # ZFS legacy mounts: > SHELOB/var - /var zfs - yes - > SHELOB/opt - /opt zfs - yes - > SHELOB/home - /home zfs - yes - > # > # -- loopback mount -- begin > # loopback mount for /usr/local: > /opt/local - /usr/local lofs - yes ro,nodevices > /home/cvs - /opt/local/cvs lofs - yes rw,nodevices > # -- loopback mount -- end > > Before I added /home to vfstab, the loopback for /opt/local/cvs would > fail. > > > I'm guessing that /opt/local/cvs is *not* visible as /usr/local/cvs ??? -Kyle > HTH -- Volker > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
