Difference between revisions of "util-vserver:Fstab"
From Linux-VServer
(Add link to logging page, note about fsck'ing on the host, hint about discussion) |
|||
| Line 3: | Line 3: | ||
The file has the format as described by man 5 fstab *except*: | The file has the format as described by man 5 fstab *except*: | ||
| − | * the fifth and sixth fields (fs_freq and fs_passno) are ignored. If you need fsck to run on a device before mounting it, you have to do so by a separate means, e.g. by running it from <tt>scripts/ | + | * the fifth and sixth fields (fs_freq and fs_passno) are ignored. If you need fsck to run on a device before mounting it, you have to do so by a separate means, e.g. by running it from <tt>scripts/initialize</tt> (*not* prepre-start as fstab entries are already mounted at the time prepre-start is being run). But be sure that either fsck's input/outputs are tied to some tty (by setting <tt>/etc/vservers/guest/apps/init/tty</tt> or <tt>/etc/vservers/.defaults/apps/init/tty</tt>), or you supply one of the -y or -n options (man e2fsck) so that it can run non-interactively. But a better idea might be to run fsck from a startup script during the *host* boot process. |
| + | |||
| + | <small>There has been some discussion between <tt>Bertl</tt>, <tt>daniel_hozac</tt> and <tt>pflanze</tt> on #vserver on 2007/02/10 about adding support for the "fs_passno" ("fsck") field, but the benefit is not entirely clear.</small> | ||
| + | |||
| + | === See also === | ||
| + | |||
| + | * [[util-vserver:Logging]] on how stdin/out/err are being setup when booting vservers | ||
Revision as of 18:31, 10 February 2007
About /etc/vservers/<name>/fstab
The file has the format as described by man 5 fstab *except*:
- the fifth and sixth fields (fs_freq and fs_passno) are ignored. If you need fsck to run on a device before mounting it, you have to do so by a separate means, e.g. by running it from scripts/initialize (*not* prepre-start as fstab entries are already mounted at the time prepre-start is being run). But be sure that either fsck's input/outputs are tied to some tty (by setting /etc/vservers/guest/apps/init/tty or /etc/vservers/.defaults/apps/init/tty), or you supply one of the -y or -n options (man e2fsck) so that it can run non-interactively. But a better idea might be to run fsck from a startup script during the *host* boot process.
There has been some discussion between Bertl, daniel_hozac and pflanze on #vserver on 2007/02/10 about adding support for the "fs_passno" ("fsck") field, but the benefit is not entirely clear.
See also
- util-vserver:Logging on how stdin/out/err are being setup when booting vservers
