Lines Matching refs:storage

14 A number of complex storage technologies on Linux (e.g. RAID, volume
15 management, networked storage) require user space services to run while the
16 storage is active and mountable. This requirement becomes tricky as soon as the
17 root file system of the Linux operating system is stored on such storage
24 When complex storage technologies are used as backing for the root file system
30 file systems (and its storage backing) that could not be unmounted as long as
34 first time arbitrary complex stacks of storage technology.
36 Previous attempts to handle root file system setups with complex storage as
37 backing usually tried to maintain the root storage with program code stored on
38 the root storage itself, thus creating a number of dependency loops. Safely
40 storage needs to stay around longer than the storage, which is technically
46 As a result, we hereby clarify that we do not support storage technology setups
47 where the storage daemons are being run from the storage it maintains
48 itself. In other words: a storage daemon backing the root file system cannot be
51 What we do support instead is that these storage daemons are started from the
54 storage daemons involved with maintaining the root file system storage
81 To implement the supported logic proposed above (i.e. where storage daemons
103 clean unmounting/detaching of the root file system and its backing storage.
144 These recommendations apply to those storage daemons which need to stay around
145 until after the storage they maintain is unmounted. If your storage daemon is
146 fine with being shut down before its storage device is unmounted you may ignore
149 This all applies to storage technology only, not to daemons with any other
150 (non-storage related) purposes.
156 support storage daemons to be started from within the actual OS, for example
157 when complex storage setups are used for auxiliary file systems, i.e. not the
161 * If your storage daemon is run from the main OS (i.e. not the initrd) it will
172   off your storage daemon from udev or an administrator command you thus make
174   shut down, your storage daemon is killed too, resp. whenever the login
175   session goes away your storage might be terminated as well. (Also note that
180 * To automatically spawn storage daemons from udev rules or administrator
183   socket of your storage daemon will result in the storage to be started. For