You are not logged in.
- Topics: Active | Unanswered
#1 2019-05-20 10:25:10
- havok
- Member
- Registered: 2007-12-07
- Posts: 14
glibc oddities, hardlinks in package
I am moving my root to a new filesystem, where my newroot is composed of several zfs datasets for ease of management.
>zfs get -r exec flywheel/root/arch
NAME PROPERTY VALUE SOURCE
flywheel/root/arch exec off inherited from flywheel
flywheel/root/arch/root exec off inherited from flywheel
flywheel/root/arch/rules exec off inherited from flywheel
flywheel/root/arch/rules/bin exec on local
flywheel/root/arch/rules/bin/usr_bin exec on inherited from flywheel/root/arch/rules/bin
flywheel/root/arch/rules/bin/usr_lib exec on inherited from flywheel/root/arch/rules/bin
flywheel/root/arch/rules/bin/usr_lib32 exec on inherited from flywheel/root/arch/rules/bin
flywheel/root/arch/rules/bin/usr_local_bin exec on inherited from flywheel/root/arch/rules/bin
flywheel/root/arch/rules/bin/usr_local_lib exec on inherited from flywheel/root/arch/rules/bin
flywheel/root/arch/rules/bin/usr_local_lib32 exec on inherited from flywheel/root/arch/rules/bin
[...]
>zfs get -r mountpoint flywheel/root/arch
flywheel/root/arch mountpoint /flywheel/root/arch default
flywheel/root/arch/root mountpoint /flywheel/root/arch/root default
flywheel/root/arch/root/etc mountpoint /flywheel/root/arch/root/etc default
flywheel/root/arch/rules mountpoint /flywheel/root/arch/rules default
flywheel/root/arch/rules/bin mountpoint /flywheel/root/arch/rules/bin default
flywheel/root/arch/rules/bin/usr_bin mountpoint /flywheel/root/arch/root/usr/bin local
flywheel/root/arch/rules/bin/usr_lib mountpoint /flywheel/root/arch/root/usr/lib local
flywheel/root/arch/rules/bin/usr_lib32 mountpoint /flywheel/root/arch/root/usr/lib32 local
flywheel/root/arch/rules/bin/usr_local_bin mountpoint /flywheel/root/arch/root/usr/local/bin local
flywheel/root/arch/rules/bin/usr_local_lib mountpoint /flywheel/root/arch/root/usr/local/lib local
flywheel/root/arch/rules/bin/usr_local_lib32 mountpoint /flywheel/root/arch/root/usr/local/lib32 local
[...]glibc gave me errors during syncing, due to hardlinking across dataset/filesystem boundaries.
>rsync -aHAXxvW /oldroot/ /newroot
[...]
rsync: link "/flywheel/root/arch/root/usr/lib/getconf/POSIX_V6_LP64_OFF64" => usr/bin/getconf failed: Invalid cross-device link (18)
[...]
rsync: [sender] write error: Broken pipe (32)
Hlink node data for 25925 already has path=usr/bin/getconf (usr/lib/getconf/POSIX_V6_LP64_OFF64)
rsync error: errors with program diagnostics (code 13) at hlink.c(543) [generator=3.1.2]User jamespharvey20 previously ran across namcap errors on glibc, see thread
Now, i realize i am far from a usual or even supported configuration, but should I just solve it on my end and be on my merry way, or should I report this bug?
Last edited by havok (2019-05-20 10:49:05)
Offline
#2 2019-05-20 11:17:22
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,390
- Website
Re: glibc oddities, hardlinks in package
I'd find it hard to justify /usr/bin and /usr/lib being on different filesystems.
Offline