1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
=head1 NAME
nbdkit-client - how to mount NBD filesystems on a client machine
=head1 DESCRIPTION
For NBD exports that contain filesystems there are several approaches
to mounting them on a client machine.
To ensure the nbd kernel module is loaded you may need to do:
# echo nbd > /etc/modules-load.d/nbd.conf
This will not take effect until you reboot, so also do:
# modprobe nbd
=head2 Easy mounting at boot time
For simple setups the following method is the easiest way to get an
NBD filesystem to mount at boot. Create or edit F</etc/rc.local> or
F</etc/rc.d/rc.local>:
#!/bin/sh -
nm-online
modprobe nbd
nbd-client server /dev/nbd0
mount /dev/nbd0 /mnt
=head2 Mounting using systemd mount points
You can use systemd mount points to mount NBD filesystems at boot
and/or on demand.
Set up an L<nbdtab(5)> mapping. If F</etc/nbdtab> doesn't exist, then
create it first. Add this line:
nbd0 server / bs=512,persist
As a workaround for
L<https://github.com/NetworkBlockDevice/nbd/issues/91> you must
currently modify the F<nbd@.service> file:
# cp /usr/lib/systemd/system/nbd@.service /etc/systemd/system/
# vi /etc/systemd/system/nbd@.service
and edit or create these settings in the C<[Service]> section:
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/nbd-client %i
ExecStop=/usr/sbin/nbd-client -d /dev/%i
Finally create a systemd mount file called
F</etc/systemd/system/mnt.mount>:
[Unit]
Requires=nbd@nbd0.service
[Mount]
What=/dev/nbd0
Where=/mnt
Type=ext4
You can either reboot now or do:
# systemctl start mnt.mount
Other systemd services which need this mount point can depend on this
mount unit.
=head1 LIMITATIONS
Red Hat Enterprise Linux 8 enabled the C<nbd.ko> Linux kernel module
but only for Unix domain sockets (ie. local connections). This means
you cannot connect to an NBD server over a TCP network. This also
affects Linux distributions derived from RHEL like CentOS, Alma and
others.
This does not affect use of nbdkit as an NBD server, only the Linux
kernel as an NBD client. Userspace Linux clients such as L<libnbd(3)>
tools will work.
=head1 SEE ALSO
L<nbdkit(1)>,
L<nbdkit-loop(1)>,
L<nbdkit-service(1)>,
L<nbd-client(8)>,
L<nbdtab(5)>,
L<systemd(1)>,
L<systemd.mount(5)>.
=head1 AUTHORS
Richard W.M. Jones
=head1 COPYRIGHT
Copyright Red Hat
|
