FS#50258 - [systemd] freezes during unmount whilst shuting down

Attached to Project: Arch Linux
Opened by Mattias Andrée (maandree) - Thursday, 04 August 2016, 12:47 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 29 October 2016, 15:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

systemd “eats the filesystem”. This has been an issue since Arch Linux started using systemd and is still a problem in systemd 230-7.

During shutdown or reboot, it freezes when dettaching LUKS-encrypted swap, and no filesystem is ever unmounted, and the must be shutdown or rebooted by pressing the physical shutdown or reboot buttons.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 29 October 2016, 15:15 GMT
Reason for closing:  Upstream
Comment by Dave Reisner (falconindy) - Thursday, 04 August 2016, 13:15 GMT
You'd be the first to report such a thing. Since it's been happening for so long, could you please attach the debug logs you've collected showing exactly what systemd is doing?
Comment by Mattias Andrée (maandree) - Thursday, 04 August 2016, 13:20 GMT
I don't have any debug logs, but I can try too acquire some,
but I seldom restart my computer, so it can take quite some time.
Comment by Dave Reisner (falconindy) - Sunday, 07 August 2016, 14:36 GMT
If you're not interested in helping those whom you're asking for help, then I'm not sure why you opened this bug report.

Regardless, upstream will be interested in your findings when you get around to it. This isn't a packaging problem.
Comment by Mattias Andrée (maandree) - Sunday, 07 August 2016, 19:19 GMT
I'm not asking for help, I'm informing you about a bug in your distribution. I said that I seldom reboot, so it doesn't effect me that much, and if it did I would just use something else. I didn't say I will not help out, just that it could take a while. I will do my best to acquire debugs logs next time I reboot, but as of now it that are completely empty except for a 24-hour period in 2014.

Stop this bullshit (we often see) about bug reports being egoistic or plain harassment. When you file a bug report, you are helping out, and more would probably be filed is this attitude did not exist, and that would be good.

As for your second paragraph. Upsteam usually tell me to report it do the distro when I think it is an upstream issue. In this case, I don't know, I have not investigated it. So I'm just doing what they would tell me to do anyway.
Comment by AK (Andreaskem) - Sunday, 07 August 2016, 19:39 GMT
Maybe I should not get involved but I have to defend falconindy here. You opened a bug report about an issue that you say appeared years ago. You provide almost no information at all and when asked about more, you say that it might take a long time. Apparently this means more than a few years as you did not get around to gathering any information as of yet.

All falconindy said was that he is not sure what this bug report is supposed to accomplish then. He basically cannot do anything at all and there is no way to even start to work on this issue. Your reaction is extremely hostile and, frankly speaking, ridiculous. Falconindy did nothing even approaching what you accuse him of.
Comment by Mattias Andrée (maandree) - Sunday, 07 August 2016, 19:57 GMT
Almost four years means about three reboots (not counting closely consecutive or involuntary reboots (e.g. powerfailure)). Is it really expected of me that have troubleshooted a problem that have only happend three times when doing the troubleshoot involves turing of my computer and don't do anything else and even not have any background jobs running?

Frankly I think that closing a bug report because I haven't had time to debug a problem is being a bit hostile and akin to closing a bug report because I didn't provide a patch for the problem, which is ridiculous. It shouldn't be expected of me more than describing the symptoms. If I am however asked to try potential solutions, or descibed whys to acquire more that than could help you, I argubly should, but I am not responsible for doing so immediately. I do it when it fits me, not when it fits you. You have other problems too, so you are not in a hurry with any specific one (unless it is a critical bug, which I did not report this as).

Loading...