summaryrefslogtreecommitdiffstats
path: root/etc/rc.d/zfs
Commit message (Collapse)AuthorAgeFilesLines
* rc.d/zfs: pass -v option to zfs mountavg2013-07-091-1/+1
| | | | | | | this should make boot process more informative (and entertaining) on systems with lots of zfs filesystems. MFC after: 7 days
* Currently there is a problem with fscking UFS file systems created onpjd2009-07-291-20/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | top of ZVOLs. The problem is that rc.d/fsck runs before rc.d/zfs. The latter makes ZVOLs to appear in /dev/. In such case rc.d/fsck cannot find devfs entry and aborts. We cannot simply move rc.d/zfs before rc.d/fsck, because we first want kern.hostid to be configured (by rc.d/hostid). If we won't wait (hostid will be 0) we can reuse disks which are in use by different systems (eg. in SAN/NAS environment). We also cannot move rc.d/hostid before rc.d/fsck, because rc.d/hostid on first system start stores generated kern.hostuuid in /etc/hostid file, so it needs root file system to be mounted read-write. The fix is to split rc.d/hostid so that rc.d/hostid (which will now run before rc.d/fsck) only generates hostid and sets up sysctls, but doesn't touch root file system and rc.d/hostid_save (which is run after rc.d/root) and only creates /etc/hostid file. With that in place, we can move ZVOL initialization to dedicated rc.d/zvol script which runs before rc.d/fsck. PR: conf/120194 Reported by: James Snow <snow@teardrop.org> Reviewed by: brooks Approved by: re (kib) MFC after: 2 weeks
* As previously discussed, add the svn:executable property to all scriptsdougb2008-07-161-0/+0
|
* Back out revision 1.6, the addition of "BEFORE: mountcritremote".dougb2008-04-021-1/+0
| | | | | | | | mountcritremote REQUIREs FILESYSTEMS, and that script REQUIREs zfs, so this change is a noop. By removing it we make life a little easier both for rcorder(8) and for debugging down the road. Approved by: 2 weeks of silence from pjd
* Be sure to run rc.d/zfs before mountcritremote. This way we can for examplepjd2008-03-191-0/+1
| | | | | | configure devfs rules in /etc/devfs.conf for ZVOLs. Submitted by: Yarema <yds@CoolRat.org>
* When zfs dataset has jailed=on property, it won't be mounted withpjd2007-04-221-3/+34
| | | | | | | 'zfs mount -a' from the main system - this is by design, as mountpoint may be set to dangerous value. This all means, that such file system has to be mounted from within a jail. To make it easier, reorganize rc.d/zfs script so it can be used from within a jail.
* When org.freebsd:swap property is set to 'on' on a ZVOL, use is as a swappjd2007-04-151-0/+18
| | | | | | device. Discussed with: des
* Remove the shutdown keyword. It just adds noise to the shutdown process.des2007-04-131-1/+1
|
* - Create an empty /etc/zfs/exports file when zfs_enable="YES" and we don'tpjd2007-04-131-2/+5
| | | | | | | | | | NFS-share anything. This way we can safely start mountd with /etc/zfs/exports and mountd won't complain. Pointed out by: ceri - Move 'zfs volinit' before 'zfs mount -a' and 'zfs volfini' after 'zfs unmount -a'.
* - Add ZFS startup script.pjd2007-04-061-0/+33
Submitted by: des - When starting mountd(8) and ZFS is enabled, add /etc/zfs/exports file. - Update rc.conf(5).
OpenPOWER on IntegriCloud