Bug 8322

Summary:	systemd mount_point_ignore
Product:	Mageia	Reporter:	Alex Loginov <loginov_alex>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia
Version:	Cauldron	Keywords:	PATCH
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	patch with fix File system

Description Alex Loginov 2012-12-07 13:28:50 CET

Description of problem:

Errors with unmount ignore_paths. Patch is in attachment.
This patch added also additional paths for ignoring for distributions MagOS, MageiaOS. But this patch is needed for Mageia also.

Comment 1 Alex Loginov 2012-12-07 13:29:58 CET

Created attachment 3207 [details]
patch with fix

Alex Loginov 2012-12-07 13:30:19 CET

Keywords: (none) => PATCH

Alex Loginov 2012-12-07 13:30:43 CET

Hardware: i586 => All

Manuel Hiebel 2012-12-07 15:31:29 CET

CC: (none) => mageia

Comment 2 Colin Guthrie 2012-12-07 16:12:26 CET

Can you describe the problem in more depth?

I don't like the idea of patching this file continuously and would rather find an alternative solution.

I'd rather that these file systems are attempted to be unmounted and fail in systemd but then are handed back over the initramfs which should deconstruct them properly - there are already appropriate mechanisms in place to do that, so would rather use them if possible.

Comment 3 Alex Loginov 2012-12-07 18:41:49 CET

/mnt/live, /mnt/livemedia, /mnt/liveloop are used by Mageia-based distributions. Filesystems: aufs or unionfs. When systemd are unmounting this directories (when poweroff or restart), then there are many-many errors on display. That's why we needs patch for systemd. But you can find an alternative solution.

Comment 4 Alex Loginov 2012-12-08 11:15:44 CET

Created attachment 3214 [details]
File system

Comment 5 Alex Loginov 2012-12-08 11:18:47 CET

On picture I show how file system is used. I hope it will help to you.

Comment 6 Colin Guthrie 2013-01-06 19:15:56 CET

The errors from systemd shouldn't really be errors as such, just information stating that certain paths cannot be unmounted.

Does this result in any actual delays or anything or is it just for the reasons of cosmetics that you want to hide such warnings?

As far as I know, the same messages/warnings would be shown for /usr if you opt to have that on a separate partition.

Comment 7 Alex Loginov 2013-01-06 21:03:50 CET

Please, hide messages for cosmetics.

Comment 8 Colin Guthrie 2013-06-13 23:07:54 CEST

So I've had a think about this and I don't really like the idea of patching systemd to ignore these specific paths.

In more recent systemd's there is a mount option to specify that certain mount points be handled in the initrd (x-initrd.mount). This is currently only used in the fstab generator, but IMO it should probably be extended to the unmounting logic also.

Using this system (assuming it's fixed slightly upstream) should allow you to specify certain mount points that are basically not handled in this logic and thus delegated to something further up the stack.

I'll mention the lack of x-initrd.mount in the umount logic to upstream guys, but in the mean time this is a wontfix I'm afraid.

All the best.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX