search for: devicemapper

Hi All. I am currently running docker 1.13 on Centos 7 boxes with devicemapper storage plugin. I would like to know what are your experiences in regard to: - storage plugins - kernel versions - stability I consider upgrade to docker 17.03.1 and would like to choose most stable combination of kernel/storage plugin. Thanks for all info! BR, Rafal.

I'm looking for people who have an xbox360 joystick to help run some tests so I can get information on implementing xinput for wine. The more 360 joysticks plugged in the better. Can you please go to the forum post I made and test: http://forum.freegamedev.net/index.php?t=msg&th=1980&start=0 Thanks, Andrew

...-ostree-client-2017.6-6.atomic.el7.x86_64 ## OverlayFS Storage In previous releases of CentOS Atomic Host, SELinux had to be in permissive or disabled mode for OverlayFS storage to work. Now you can run the OverlayFS file system with SELinux in enforcing mode. CentOS Atomic Host still defaults to devicemapper storage, but you can switch to OverlayFS using the following commands: $ systemctl stop docker $ atomic storage reset # Reallocate space to the root VG - tweak how much to your liking $ lvm lvextend -r -l +50%FREE atomicos/root $ atomic storage modify --driver overlay2 $ systemctl start docker...

..., for two purposes : A/ allowing "freezing" in a clean state, to allow clean snapshotting B/ allowing "freezing" while moving a SCSI disk or a network-connected disk without umounting filesystem A/ would require some work at the FS layer I guess, but B/ might be doable at the devicemapper layer or something like that. 3) Is it possible to allow data to stay in the journal for a very long time ? Rationale : for laptops with a lot of memory and some solid-state memory, this would allow to shutdown the hard disk (if all read data is in the cache, and all written data goes to the lo...

I have a CentOS 5 machine in which I'm trying to remove lvm. I dd'ed the file system to another partition, then dd'ed it back overwriting the lvm partition. I then modified menu.lst and fstab and replaced the paths to point to the correct device. When the system boots it's still looking for lvm. I can restore the system back to where it was with lvm, but I'm not sure what

...-ostree-client-2017.6-6.atomic.el7.x86_64 ## OverlayFS Storage In previous releases of CentOS Atomic Host, SELinux had to be in permissive or disabled mode for OverlayFS storage to work. Now you can run the OverlayFS file system with SELinux in enforcing mode. CentOS Atomic Host still defaults to devicemapper storage, but you can switch to OverlayFS using the following commands: $ systemctl stop docker $ atomic storage reset # Reallocate space to the root VG - tweak how much to your liking $ lvm lvextend -r -l +50%FREE atomicos/root $ atomic storage modify --driver overlay2 $ systemctl start docker...

hello everyone. i guess this has been asked before, but haven't found it in the faq. i have the following issue... it is not uncommon nowadays to have desktops with filesystems in the order of 500gb/1tb. now, my kubuntu (but other distros do the same) forces a fsck on ext3 every so often, no matter what. in the past it wasn't a big issue. but with sizes increasing so much, users are