Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29636 - [dmraid] fix pathes

Attached to Project: Arch Linux
Opened by Christian Hesse (eworm) - Friday, 27 April 2012, 06:40 GMT
Last edited by Tom Gundersen (tomegun) - Friday, 04 May 2012, 11:23 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
The dmraid mkinitcpio hook adds udev rule files from /lib/ which were moved to /usr/lib/ with the last device-mapper update. This patch fixes it and moves dmraid itself to /usr.

Additional info:
dmraid 1.0.0.rc16.3-2
   dmraid.patch (1.9 KiB)
This task depends upon

Closed by  Tom Gundersen (tomegun)
Friday, 04 May 2012, 11:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  testing
Comment by Tobias Powalowski (tpowa) - Friday, 27 April 2012, 16:19 GMT
it's already semi fixed in testing
Comment by Oracle Speaks (test0987654321) - Tuesday, 01 May 2012, 10:05 GMT
Why does dmraid need these two lines in the dmraid PKGBUILD file?

mkdir -p "$pkgdir"/var/lock/dmraid
chmod 1777 "$pkgdir"/var/lock/

The folder /var/lock is a symlink to /run/lock and /run/lock is using tmpfs. So anything sent to /var/lock will end up in /run/lock and will not survive a reboot. When I install dmraid and reboot I get this warning messege from pacman -Qk

warning: dmraid: /var/lock/dmraid/ (No such file or directory)
dmraid: 37 total files, 1 missing file

The folder /var/lock/dmraid is lost because it was stored in tmpfs. Even though the folder is lost during a reboot and not recreated during a bootup, dmraid works fine without this folder. Why is it created during a dmraid install? It does not seem to be needed. Should the two PKGBUILD lines be removed?

The folder /var/lock/dmraid is the only warning message I get from pacman -Qk

Thanks for you help.
Comment by Alexander Artyukhin (artyukhin) - Tuesday, 01 May 2012, 22:39 GMT
it's make system unbootable!
Comment by Oracle Speaks (test0987654321) - Wednesday, 02 May 2012, 08:54 GMT
What makes your system unbootable? Is it the dmraid.patch, the bug the patch is supposed to fix, or is it my suggestion to remove the above two lines from the PKGBUILD file?
Comment by Alexander Artyukhin (artyukhin) - Wednesday, 02 May 2012, 09:17 GMT
No, patch is good. Bug makes unbootable and buggy package is still in repo.
Comment by Tom Gundersen (tomegun) - Wednesday, 02 May 2012, 11:17 GMT
is this fixed for you guys with the package in testing?
Comment by Christian Hesse (eworm) - Friday, 04 May 2012, 07:31 GMT
dmraid and dmevent_tool still resist in /sbin/. Is this expexted or do we want to move these to /usr/sbin/?

However I get some errors while my backup script takes read only snapshots:

/usr/sbin/dmeventd: stat failed: No such file or directory
/usr/sbin/dmeventd: stat failed: No such file or directory
cvg-snap--1336116331--home: event registration failed: No such process
cvg/snapshot0: snapshot segment monitoring function failed.

Not sure if dmraid or device-mapper is responsible for that.
Comment by Christian Hesse (eworm) - Friday, 04 May 2012, 09:07 GMT
The dmeventd issue is caused by lvm2 (which is a split package for lvm2 and device-mapper). Will report a new bug shortly.

So I am fine with dmraid from testing.
Comment by Tom Gundersen (tomegun) - Friday, 04 May 2012, 11:22 GMT
We probably don't want to move these tools yet, as we'll get problems with other scripts relying on their location. They will probably be moved together with the rest of /bin, /sbin (to /usr/bin, not /usr/sbin) when we replace the folders by symlink. I'll close this issue as fixed.

Loading...