Bug 743024 - fails w/ 'File not found by ext2_lookup' due to crossmount symlink on host filesystem
Summary: fails w/ 'File not found by ext2_lookup' due to crossmount symlink on host f...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: supermin
Version: 19
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-03 15:51 UTC by Bowe Strickland
Modified: 2015-02-17 13:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:54:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
debugging output of failing libguestfs mount (7.38 KB, application/octet-stream)
2011-10-03 15:51 UTC, Bowe Strickland
no flags Details

Description Bowe Strickland 2011-10-03 15:51:53 UTC
Created attachment 526090 [details]
debugging output of failing libguestfs mount

After an oz install of a JEOS image, post configuration fails because libguestfs fails to mount the image with:

>> febootstrap-supermin-helper: ext2: parent directory not found: /home/local: >> File not found by ext2_lookup

Image subsequently manually boots w/o issue.

Oddly, /home/local exists as a symlink target on the host, not the guest, and renaming the target to /home/local.o (breaking the link) resolves the issue.

More info:  

>> [root@alien ~]# uname -r
>> 2.6.40.3-0.fc15.x86_64
>> [root@alien ~]# rpm -q libguestfs
>> libguestfs-1.10.9-1.fc15.x86_64

I've installed local laptop separating "data" as /home from "system" as root directory /, then symlink /usr/local --> /home/local.


>> [bowe@alien oz]$ ll /usr/local
>> lrwxrwxrwx. 1 root root 11 May 26 08:41 /usr/local -> /home/local

>> [bowe@alien oz]$ sudo virt-df /var/lib/libvirt/images/aeolus_rhel6.dsk
>> febootstrap-supermin-helper: ext2: parent directory not found: /home/local: 
>> File not found by ext2_lookup

renaming the symlink target, however (and thus breaking the link), things work:

>> [bowe@alien oz]$ sudo mv /home/local /home/local.o
>> [bowe@alien oz]$ sudo virt-df /var/lib/libvirt/images/aeolus_rhel6.dsk
>> Filesystem                           1K-blocks       Used  Available  Use%
>> aeolus_rhel6.dsk:/dev/sda1              198337      26652     161445   14%
>> aeolus_rhel6.dsk:/dev/VolGroup00/LogVol00
>>                                        8547036    1023520    7089340   12%

Full trace of failure attached.

Comment 1 Richard W.M. Jones 2011-10-03 16:14:51 UTC
This is a bug in febootstrap-supermin-helper (even in latest
version 3.10).  Reassigning ...

I should say it's not so easy to fix.  You might want to
work around it by removing the /usr/local/* lines in
the file /usr/lib*/guestfs/supermin.d/hostfiles

Comment 2 Bowe Strickland 2011-10-03 19:37:09 UTC
yep, works. thanks for workaround!

Comment 3 Richard W.M. Jones 2013-02-09 14:06:43 UTC
'febootstrap' named to 'supermin' in Fedora 19.

Comment 4 Peter Robinson 2013-03-18 16:35:14 UTC
I've seen this on RHEL 6.4. Interestingly it was working fine last week. Started playing up this week. Testing the removal of /usr/local

Comment 5 Richard W.M. Jones 2013-03-19 11:54:53 UTC
(In reply to comment #4)
> I've seen this on RHEL 6.4. Interestingly it was working fine last week.
> Started playing up this week. Testing the removal of /usr/local

The issue was found to be that Peter didn't have enough free
space on /tmp or /var/tmp for the libguestfs appliance to
be built.

Comment 6 Fedora End Of Life 2013-04-03 17:22:42 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 7 Fedora End Of Life 2015-01-09 16:48:31 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 8 Fedora End Of Life 2015-02-17 13:54:42 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.