Truong, thanks again for the response. I shall implement what is suggested in the FAQ. As we are in polite company I shall maintain a smiley face when mentioning systemd
From: John Hearns Sent: Wednesday, August 02, 2017 4:49 PM To: 'gpfsug main discussion list' <gpfsug-discuss@spectrumscale.org> Subject: RE: [gpfsug-discuss] Systemd will not allow the mount of a filesystem Truong, thankyou for responding. The discussion which Renar referred to discussed system version 208, and suggested upgrading this. The system I am working on at the moment has systemd version 219, and there is only a slight minor number upgrade available. I should say that the temporary fix suggested in that discussion did work for me. From: gpfsug-discuss-boun...@spectrumscale.org<mailto:gpfsug-discuss-boun...@spectrumscale.org> [mailto:gpfsug-discuss-boun...@spectrumscale.org] On Behalf Of Truong Vu Sent: Wednesday, August 02, 2017 4:35 PM To: gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org> Subject: Re: [gpfsug-discuss] Systemd will not allow the mount of a filesystem This sounds like a known problem that was fixed. If you don't have the fix, have you checkout the around in the FAQ 2.4? Tru. [Inactive hide details for gpfsug-discuss-request---08/02/2017 06:51:02 AM---Send gpfsug-discuss mailing list submissions to gp]gpfsug-discuss-request---08/02/2017 06:51:02 AM---Send gpfsug-discuss mailing list submissions to gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org> From: gpfsug-discuss-requ...@spectrumscale.org<mailto:gpfsug-discuss-requ...@spectrumscale.org> To: gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org> Date: 08/02/2017 06:51 AM Subject: gpfsug-discuss Digest, Vol 67, Issue 4 Sent by: gpfsug-discuss-boun...@spectrumscale.org<mailto:gpfsug-discuss-boun...@spectrumscale.org> ________________________________ Send gpfsug-discuss mailing list submissions to gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org> To subscribe or unsubscribe via the World Wide Web, visit http://gpfsug.org/mailman/listinfo/gpfsug-discuss<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss&data=01%7C01%7Cjohn.hearns%40asml.com%7Cac94a7458386436b1f9808d4d9b3bbb5%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=LisPaZ6DUvBHZ36%2FdJspCmT3os6iXBYKgBo6WSvWTzg%3D&reserved=0> or, via email, send a message with subject or body 'help' to gpfsug-discuss-requ...@spectrumscale.org<mailto:gpfsug-discuss-requ...@spectrumscale.org> You can reach the person managing the list at gpfsug-discuss-ow...@spectrumscale.org<mailto:gpfsug-discuss-ow...@spectrumscale.org> When replying, please edit your Subject line so it is more specific than "Re: Contents of gpfsug-discuss digest..." Today's Topics: 1. Re: Systemd will not allow the mount of a filesystem (John Hearns) ---------------------------------------------------------------------- Message: 1 Date: Wed, 2 Aug 2017 10:50:29 +0000 From: John Hearns <john.hea...@asml.com<mailto:john.hea...@asml.com>> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org>> Subject: Re: [gpfsug-discuss] Systemd will not allow the mount of a filesystem Message-ID: <he1pr02mb145032fe2515fe6d091d69de88...@he1pr02mb1450.eurprd02.prod.outlook.com<mailto:he1pr02mb145032fe2515fe6d091d69de88...@he1pr02mb1450.eurprd02.prod.outlook.com>> Content-Type: text/plain; charset="utf-8" Thankyou Renar. In fact the tests I am running are in fact tests of a version upgrade before we do this on our production cluster.. From: gpfsug-discuss-boun...@spectrumscale.org<mailto:gpfsug-discuss-boun...@spectrumscale.org> [mailto:gpfsug-discuss-boun...@spectrumscale.org] On Behalf Of Grunenberg, Renar Sent: Wednesday, August 02, 2017 12:01 PM To: 'gpfsug main discussion list' <gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org>> Subject: Re: [gpfsug-discuss] Systemd will not allow the mount of a filesystem Hallo John, you are on a backlevel Spectrum Scale Release and a backlevel Systemd package. Please see here: https://www.ibm.com/developerworks/community/forums/html/topic?id=00104bb5-acf5-4036-93ba-29ea7b1d43b7&ps=25<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fdeveloperworks%2Fcommunity%2Fforums%2Fhtml%2Ftopic%3Fid%3D00104bb5-acf5-4036-93ba-29ea7b1d43b7%26ps%3D25&data=01%7C01%7Cjohn.hearns%40asml.com%7Cac94a7458386436b1f9808d4d9b3bbb5%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=NrcKNIaFZwjSd6RpoYNpHybtfUuxWOR%2BdPNfx21RKDY%3D&reserved=0><https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fdeveloperworks%2Fcommunity%2Fforums%2Fhtml%2Ftopic%3Fid%3D00104bb5-acf5-4036-93ba-29ea7b1d43b7%26ps%3D25&data=01%7C01%7Cjohn.hearns%40asml.com%7Caf48038c0f334674b53208d4d98d739e%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=XuRlV4%2BRTilLfWD5NTK7n08m6IzjAmZ5mZOwUTNplSQ%3D&reserved=0> Renar Grunenberg Abteilung Informatik ? Betrieb HUK-COBURG Bahnhofsplatz 96444 Coburg Telefon: 09561 96-44110 Telefax: 09561 96-44104 E-Mail: renar.grunenb...@huk-coburg.de<mailto:renar.grunenb...@huk-coburg.de> Internet: www.huk.de<http://www.huk.de<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.huk.de&data=01%7C01%7Cjohn.hearns%40asml.com%7Cac94a7458386436b1f9808d4d9b3bbb5%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=TAz5Wle%2BEu%2FuAEfB6P50jz2ceeSS4H8MSkFPtbNH%2FG0%3D&reserved=0>> ________________________________ HUK-COBURG Haftpflicht-Unterst?tzungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021 Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin. Vorstand: Klaus-J?rgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Her?y, Dr. J?rg Rheinl?nder (stv.), Sarah R?ssler, Daniel Thomas (stv.). ________________________________ Diese Nachricht enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet. This information may contain confidential and/or privileged information. If you are not the intended recipient (or have received this information in error) please notify the sender immediately and destroy this information. Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden. ________________________________ Von: gpfsug-discuss-boun...@spectrumscale.org<mailto:gpfsug-discuss-boun...@spectrumscale.org> [mailto:gpfsug-discuss-boun...@spectrumscale.org] Im Auftrag von John Hearns Gesendet: Mittwoch, 2. August 2017 11:50 An: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org>> Betreff: [gpfsug-discuss] Systemd will not allow the mount of a filesystem I am setting up a filesystem for some tests, so this is not mission critical. This is on an OS with systemd When I create a new filesystem, named gpfstest, then mmmount it the filesystem is logged as being mounted then immediately dismounted. Having fought with this for several hours I now find this in the system messages file: Aug 2 10:36:56 tosmn001 systemd: Unit hpc-gpfstest.mount is bound to inactive unit dev-gpfstest.device. Stopping, too. I stopped then started gpfs. I have run a systemctl daemon-reload I created a new filesystem, using the same physical disk, with a new filesystem name, testtest, and a new mountpoint. Aug 2 11:03:50 tosmn001 systemd: Unit hpc-testtest.mount is bound to inactive unit dev-testtest.device. Stopping, too. GPFS itself logs: Wed Aug 2 11:03:50.824 2017: [I] Command: successful mount testtest Wed Aug 2 11:03:50.837 2017: [I] Command: unmount testtest Wed Aug 2 11:03:51.192 2017: [I] Command: successful unmount testtest If anyone else has seen this behavior please let me know. I found this issue https://github.com/systemd/systemd/issues/1741<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsystemd%2Fsystemd%2Fissues%2F1741&data=01%7C01%7Cjohn.hearns%40asml.com%7Cac94a7458386436b1f9808d4d9b3bbb5%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=uzxQLLZFRBSs3m3W1conYQXQIp4KkH5oNtuAirfCJS4%3D&reserved=0><https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsystemd%2Fsystemd%2Fissues%2F1741&data=01%7C01%7Cjohn.hearns%40asml.com%7Caf48038c0f334674b53208d4d98d739e%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=MNPDZ4bKsQBtYiz0j6SMI%2FCsKmnMbrc7kD6LMh0FQBw%3D&reserved=0> However the only suggested fix is a system daemon-reload, and if this doesn?t work ??? Also if this is a stupid mistake on my part, I pro-actively hang my head in shame. -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt. -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20170802/c0c43ae8/attachment.html<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgpfsug.org%2Fpipermail%2Fgpfsug-discuss%2Fattachments%2F20170802%2Fc0c43ae8%2Fattachment.html&data=01%7C01%7Cjohn.hearns%40asml.com%7Cac94a7458386436b1f9808d4d9b3bbb5%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=gjIZziC5a%2BXKObsMmsBAc2yUKwevpaOoEnV4ioDpyaw%3D&reserved=0>> ------------------------------ _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss&data=01%7C01%7Cjohn.hearns%40asml.com%7Cac94a7458386436b1f9808d4d9b3bbb5%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=LisPaZ6DUvBHZ36%2FdJspCmT3os6iXBYKgBo6WSvWTzg%3D&reserved=0> End of gpfsug-discuss Digest, Vol 67, Issue 4 ********************************************* -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
