Re: [systemd-devel] systemd 210 - mount/umount/remount
Hi Karel, >On Fri, Oct 14, 2016 at 12:06:00PM +0200, Michael Hirmke wrote: >> Hi *, >> >> I've read the man pages and some more documentation about the mount >> behaviour of systemd, but I couldn't find a definitive answer to my >> questions. >> I have a backup script, that copies all files to backup to a hard disk >> partition, then duplicates the partition to one on a second disk, which >> in turn is changed every day. Before duplicating, the script tries to >> umount the partition on the original disk, does an fsck and then mounts >> the partition read only. When duplicating is finished, the original >> partition is remounted read write again. >Not sure if you copy individual files or all partition (dd(1) or so), >but would be enough to use fsfreeze(8) to avoid umount/mount? I copy individual files with rsync. Therefore I want to make sure, the original partition is clean. >I guess you can call fsck on duplicated partition on the second disk. No, because when copying individual files I never can be sure, that everything goes right. >IMHO fsfreeze is less invasive than umount. Or use LVM snapshots ;-) I know :) But that is not what I need. >Karel Thx and bye. Michael. -- Michael Hirmke ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd 210 - mount/umount/remount
On Fri, Oct 14, 2016 at 12:06:00PM +0200, Michael Hirmke wrote: > Hi *, > > I've read the man pages and some more documentation about the mount > behaviour of systemd, but I couldn't find a definitive answer to my > questions. > I have a backup script, that copies all files to backup to a hard disk > partition, then duplicates the partition to one on a second disk, which > in turn is changed every day. Before duplicating, the script tries to > umount the partition on the original disk, does an fsck and then mounts > the partition read only. When duplicating is finished, the original > partition is remounted read write again. Not sure if you copy individual files or all partition (dd(1) or so), but would be enough to use fsfreeze(8) to avoid umount/mount? I guess you can call fsck on duplicated partition on the second disk. IMHO fsfreeze is less invasive than umount. Or use LVM snapshots ;-) Karel -- Karel Zak http://karelzak.blogspot.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Fedora 25, cgroups V2 and systemd roadmap
On Tue, Oct 11, 2016 at 11:30:40PM +0300, Kevin Wilson wrote: > Hello, Daniel, > > > We don't want to support out of tree kernel patches, > > This sounds very reasonable, I don't have anything against this policy. > > Still, I wonder: are you ruling out implementing "hybrid mode" (like > Lennart uses in systemd) for libvirt? I mean a mode where you will use > the 3 currently supported cgroup V2 controllers for libvirt (memory, > io and pids; actually I don't know if you use the cgroups pids at all > in libvirt, it is a new controller; BTW - do you ? ). And using other > controllers (besides io, memory and pids) from cgroup V1 A controller can only be used in one mode at any time - so while libvirt could potentially support using some in v1 mode and some in v2 mode, it only works if the OS distro has actually setup those controllers in v1 mode - if they're in v2 mode, we'd be forced to use them in v2 mode. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o-http://search.cpan.org/~danberr/ :| ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
