On Sun, May 18, 2014 at 10:20 AM, The Wanderer <[email protected]> wrote: > On 05/18/2014 09:52 AM, Pascal Hambourg wrote: >> Tom H a écrit : >>> >>> If you have loop compiled in to the kernel, as I do below, you can >>> only change the number of loop devices at boot by using >>> "max_loop=<number_of_loop_devices" on the kernel cmdline. >>> >>> But if loop is compiled as module >>> >>> # rmmod loop >>> # modprobe loop max_loop=<number_loop_devices_minus_one> >> >> One more general piece of information about module parameters : some >> may be modified on the fly by writing into >> /sys/module/<module>/parameters/<parameter>. But it appears that >> /sys/module/loop/parameters/max_loop is read only. > > What does 'modprobe -r loop' do to any active loop devices? > > I would expect it to either error out without removing the module if any > loop devices are in use, or automatically shut the loop devices down.
Correct, the call to modprobe will fail if "loop.ko" is in use. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/CAOdo=sz4s-kk-5dmgypp1+jv5ynrsg2votnabw8j7df26on...@mail.gmail.com
