On 01/14/2015 04:47 AM, Michael Hamilton wrote:
On Tue, 13 Jan 2015, Florian Gleixner wrote:
On 01/09/2015 02:15 PM, Mark Hounschell wrote:
I am running 13.2 (x86-64). I have several (removal) disks in the box. I manually unmount one and install another in its place to mount and use temporarily. When done I will put the original disk back in and remount it manually. I get this from systemd complaining about the old disk no longer being there.
systemd[1]: Timed out waiting for device ST3160815AS. systemd[1]: Dependency failed for "blablabla".
Over and over and over for every partition on it that is defined in the fstab file.
What is this? My fstab has "ext4 defaults" for all the partitions on the disk. I think I read a thread here about a similar issue some time back but all I don't think I ever saw a real resolution. It had never affected me at the time. Not sure why, but it sure is now. What is the proper "systemd" way of doing this sort of thing now? Please don't tell me that this is no longer allowed.
Thanks Mark
Systenmd also is able to replace fstab - or parts of it. On systemd linux systems nowadays you sometimes only see real devices in /etc/fstab and a unit generator "systemd-fstab-generator" generates systemd units from the fstab. To see the filesystems systemd controls, see systemctl -a -t mount
Another feature of systemd are dependencies. So if systemd wants to mount a filesystem, it can wait for a device to appear before. Use
systemd list-dependencies
to inspect this.
I think you have to cleanup something, that came from installation time or use
systemctl disable blabla.mount
instead of simply umount. Just a guess, i did not try ...
Based on my own experiences, this might be the issue. I did a umount on a disk listed in /etc/fstab do do some maintenance on it, while I was working on it systemMd noted it was not longer mounted and remounted it for me. So trying to mount/unmount disks that are listed in /etc/fstab is dangerous without first informing systemMd either by the above mentioned disabled or perhaps a noauto in /etc/fstab.
Very unexpected behaviour for old timers.
What I found was that systemd would not attempt to remount it unless it was actually removed and then reinstalled. Or powered off then on. I'm thinking that my original problem might have been that I may have inadvertently powered down then up then down again. Systemd seems only to attempt a remount if it is re-attached or powered up. Simply unmounting then powering down of the disk causes systemd to do nothing. Which is good. I can live with the remount after powering it back up. Unexpected yes, but OK with me. Regards Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org