Bug 1214069
Summary: | Btrfs array is often unmounted right after mounting it | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Basic Six <drbasic6> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | johannbg, jsynacek, kzak, lnykryn, msekleta, s, systemd-maint, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-03 12:55:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Basic Six
2015-04-21 21:02:35 UTC
This may be related. Those 5 lines appear in /var/log/messages: Apr 21 23:01:38 server systemd: Job dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dsas\x2d0x0000000000000000\x2dlun\x2d0.device/start timed out. Apr 21 23:01:38 server systemd: Timed out waiting for device dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dsas\x2d0x0000000000000000\x2dlun\x2d0.device. Apr 21 23:01:38 server systemd: Dependency failed for /data. Apr 21 23:01:38 server systemd: Apr 21 23:01:38 server systemd: This is how it should be mounted on boot, according to fstab: /dev/disk/by-path/pci-0000:02:00.0-sas-0x0000000000000000-lun-0 /data btrfs defaults,compress=lzo,nofail 0 0 Is systemd thinking that something timed out and then unmounting it, even though the mount worked? Same error using Arch Linux on same system. journalctl -xr: systemd[1]: Unmounting /data... -- Subject: Unit data.mount has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit data.mount has begun shutting down. systemd[1]: Unit data.mount is bound to inactive unit. Stopping, too. kernel: BTRFS: has skinny extents kernel: BTRFS info (device sde): disk space caching is enabled Even manually adding TimeoutSec=0 to /run/systemd/generator/data.mount doesn't prevent systemd from timing out: # time systemctl start data.mount ; df /data/ Warning: data.mount changed on disk. Run 'systemctl daemon-reload' to reload units. A dependency job for data.mount failed. See 'journalctl -xe' for details. real 1m0.103s user 0m0.000s sys 0m0.007s Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 14510000 1536552 12213336 12% / Found a workaround: Remove it from fstab and mount it manually Sounds like bug #1226528. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Is this related to systemd issue 1788? https://github.com/systemd/systemd/issues/1788 This is very likely to be the same issue. *** This bug has been marked as a duplicate of bug 1226528 *** |