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!
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!
FS#39090 - [mkinitcpio] fails to build default image when a specific FUSE filesystem is mounted
Attached to Project:
Arch Linux
Opened by Wesley Merkel (ooesili) - Saturday, 01 March 2014, 18:35 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 01 March 2014, 21:40 GMT
Opened by Wesley Merkel (ooesili) - Saturday, 01 March 2014, 18:35 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 01 March 2014, 21:40 GMT
|
Details"# mkinitcpio -p linux" fails to build the default image when I have a specific FUSE filesystem mounted. The failure happens with the default HOOKS and with the customized HOOKS that I usually use. have attached a log that shows the failure.
The FUSE filesystem that causes the error when mounted is a just a little project that I thew together: <https://github.com/ooesili/flac-fs> but that is not really important. The reason mkinitcpio fails is because of the information that the filesystem displays with the "findmnt" utility. When mounted, the line returned from "findmnt" says the the SOURCE is "/", and the FSTYPE is "fuse./". The autodetect install-hook uses the command "$(find -uno fstype '/')" to determine the type of the root filesystem. When my FUSE filesystem is mounted, that command returns "fuse./", because findmnt searches the SOURCE column for matches before searching the TARGET column. I've included a patch that fixes this issue. If you wish to repoduce the bug, you can download and make my project, and mount it anywhere, but you have to use an absolute path for the first argument, so that the SOURCE column under findmnt displays '/'. Now, you may be thinking that this is a bug with my project, or FUSE, but any filesystem mount that has '/' under the SOURCE column, and has a FSTYPE that doesn't correlate to a fsck.* command, will cause this bug. |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 01 March 2014, 21:40 GMT
Reason for closing: Fixed
Additional comments about closing: https://projects.archlinux.org/mkinitcpi o.git/commit/?id=869c314159497c74aa6cf47 7862629b05a9fd2b0
Saturday, 01 March 2014, 21:40 GMT
Reason for closing: Fixed
Additional comments about closing: https://projects.archlinux.org/mkinitcpi o.git/commit/?id=869c314159497c74aa6cf47 7862629b05a9fd2b0
Comment by Dave Reisner (falconindy) -
Saturday, 01 March 2014, 21:40 GMT
Thanks, this needed to be fixed in more places than just where you patch points out.
mkinitcpio-autodetect-FUSE.pa...