[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #42, bug #8 (project grub): Thank you and everyone who helped. ___ Reply to this item at: ___ Message sent via/by Savannah http:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Update of bug #8 (project grub): Status:None => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #41: Fixed in 5370dcfdae66

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #40, bug #8 (project grub): Will you commit this now? Or should other tests be done? ___ Reply to this item at: ___ Message sent v

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #39, bug #8 (project grub): Yes, it does. Thank you very much for assistance. ___ Reply to this item at: ___ Message sent via/by S

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #38, bug #8 (project grub): Yes, size was truncated. Please revert previous patch and test this one - should fix it. (file #34000) ___ Additional Item Attachment: File name: 8v2.patch Size:1 KB

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #37, bug #8 (project grub): Tested, not showing the file yet. Here's the log. (file #33998) ___ Additional Item Attachment: File name: grub-fstest.logSize:18 KB __

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #36, bug #8 (project grub): Please test with attached patch (which shows size before shift). Attach usual debug log from attempt to list non-existing file. (file #33987) ___ Additional Item Attachment: File name:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #35, bug #8 (project grub): Well, I don't know how to check the overflow of any variables, sorry. I can only state that reverting this small change in gurb-core/fs/zfs/zfs.c in the latest git code makes everything work again. And for the information, /boot/kernel directory i

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #34, bug #8 (project grub): ah, ok, i think i can see what is going on there -- the mzap itself has indeed number of chunks defined as 16bit int, meaning that single mzap entry can not have more; however, in case of large directory, there are probably more mzap entries in use

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #33, bug #8 (project grub): So, here is my result: 87a04adb6541c4bf169644bb2f84036a7c8558dd is the first bad commit commit 87a04adb6541c4bf169644bb2f84036a7c8558dd Author: Vladimir Serbinenko Date: Sat Feb 21 16:22:01 2015 +0100 zfs/mzap_lookup: Fix argument types :

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #32, bug #8 (project grub): OK got it. ___ Reply to this item at: ___ Message sent via/by Savannah http://savannah.gnu.org/ __

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #31, bug #8 (project grub): Th problem with git bisect command is that it doesn't recognize the version of 2.02~beta2: fatal: Needed a single revision Bad rev input: 2.02~beta2 ___ Reply to this item at:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #30, bug #8 (project grub): arvidjaar: Thanks for your detailed recommendation on git bisect. I'll try as soon as I have time. ___ Reply to this item at: __

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #29, bug #8 (project grub): ok, from this debug list it appears its getting full listing without the errors, did you compare this full listing with real ls command output? was there anything missing? at least the zfs.ko, which was used in some previous examples was listed the

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #28, bug #8 (project grub): OK, attached the output of the command: grub-fstest -d zfs /dev/ada0 ls /ROOT/default@/boot/kernel > debug.txt 2>&1 (file #33952) ___ Additional Item Attachment: File name: debug.txt.bz2

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #27, bug #8 (project grub): ok, thanks, the code is the same. so, can you post the command and debug output for listing files in that /boot/kernel please. the full directory, not just one file. to save space you can compress it, i understand you have quite many files there

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #26, bug #8 (project grub): I've emailed you the zfs.c. As to your version of events, I'll tell you how I created this installation. I deleted all partitions from the disk, then created a ZFS pool all over the disk (raw-disk pool). Then sent a snapshot from my existing inst

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #25, bug #8 (project grub): just to clarify why i'm insisting to check with extendible dataset patch - since freebsd zfs does implement it, it *may* be the case the actual write did use this feature but did not update feature flag properly, in which case the updated read test

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #24, bug #8 (project grub): Were you able to apply the patch cleanly and can you mail me the zfs.c? If patch was successful, please post an full debug log from "grub-fstest ls /ROOT/default/@/boot/kernel" with command line you used. Also please try to paste the actual comma

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #23, bug #8 (project grub): No. It works for my other pool, which doesn't have these features enabled. Toomas Soome:No, the actual command was grub-fstest /dev/ada0 ls /ROOT/goot/kernel/zfs.ko I start from the start, with the 'ls' command for root: grub-fstest /dev/ada0 ls

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Update of bug #8 (project grub): Category:Terminal => Filesystem ___ Follow-up Comment #22: If you are sure it worked in 2.02~beta2 then as I already told you the most straightforward way to

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #21, bug #8 (project grub): just for future reference; your current grub-fstest ls command fails because you are running it as "ls /boot/kernel", but you need to run it as "ls /@/boot/kernel" - the boot is directory on dataset, and dataset root is specified by /@/. or if you

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #20, bug #8 (project grub): Yes, please, post it in git format or something. Copy pasting causes line breaking sometimes, so there appear "lines" that aren't present in the code. ___ Reply to this item at:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #19, bug #8 (project grub): uh, which part were left out? i can post you git format-patch, so you should get it applied clean and we can be sure we are on the same code base:) ___ Reply to this item at:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #18, bug #8 (project grub): Sorry, there was a typo in the command ("goot" instead of "boot"). With the typo corrected the output is like this: grub-core/fs/zfs/zfs.c:1192: label ok 0 grub-core/fs/zfs/zfs.c:1007: check 2 passed grub-core/fs/zfs/zfs.c:1018: check 3 passed gru

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #17, bug #8 (project grub): Yes, I applied some parts manually. Here's the output: grub-core/fs/zfs/zfs.c:1192: label ok 0 grub-core/fs/zfs/zfs.c:1007: check 2 passed grub-core/fs/zfs/zfs.c:1018: check 3 passed grub-core/fs/zfs/zfs.c:1025: check 4 passed grub-core/fs/zfs/zfs

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #16, bug #8 (project grub): so, do i understand correctly, you were able to apply the patch and it did not solve it? if so, can you post debug output from it? ___ Reply to this item at:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #15, bug #8 (project grub): Sorry, the patch doesn't help. BTW, the patch as you've posted it is malformed. Must be a copy-pasting error... Still, as i mentioned: when I copy the problematic files into a separate directory /boot/custom, they're loaded by grub and everything

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #14, bug #8 (project grub): can you grab patch from https://lists.gnu.org/archive/html/grub-devel/2015-04/msg00055.html and test it against version from git? from this log, I would suspect the most plausible reason is missing support for extendible dataset feature, but this

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #13, bug #8 (project grub): OK, this time things are "better": I can copy the files linux.ko, opensolaris.ko, zfs.ko (along with the corresponsing *.symbols files) over to a small custom directory, THEN grub2 can see and load these modules. At the time of the original bug rep

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #12, bug #8 (project grub): Can you still install using 2.02~beta2 (to exclude some changes in your environment)? If yes, please open separate bug report for grub-install issue; include full command invocation and its output as well grub-install --debug output. @toomas, I ho

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #11, bug #8 (project grub): Here is my log with grub-fstest -d zfs (for the problematic file): grub-core/fs/zfs/zfs.c:1190: label ok 0 grub-core/fs/zfs/zfs.c:1005: check 2 passed grub-core/fs/zfs/zfs.c:1016: check 3 passed grub-core/fs/zfs/zfs.c:1023: check 4 passed grub-core

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #10, bug #8 (project grub): can you please post zfs debug outputs; from grub itself you can set debug=zfs, with grub-fstest you can use -d zfs switch. also note that this log is pretty large, so, with grub itself you may wanna add serial output (if you have connection) to gra

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #9, bug #8 (project grub): How big is filesystem? Can you make avilable image? Alernatively, if it depends on number of files, may be you can test empty filesystem with single big directory and make image of it? Should be smaller.

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #8, bug #8 (project grub): If problem was introduced after 2.02-beta2 and you can reliably trigger it, the easiest is to use git bisect to find out bad commit. ___ Reply to this item at:

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #7, bug #8 (project grub): Hm, in case I run it like (gdb) run /dev/ada1p2 ls /ROOT/kernel/kernel (a file that's recognized by "ls -l" command) it DOES stop at the given breakpoint. But if specify the path to a "not found" file (i.e. /ROOT/working/freebsd@/boot/kernel/zfs.

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #6, bug #8 (project grub): Well, here it beats me. I'm not (yet) a C programmer, so while I can figure out how to set breakpoints in gdb, I don't know how to add "top level printf" in a C program. And without that gdb only outputs multiple "no debugging symbols found" statem

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #5, bug #8 (project grub): There are no special diagnostic options. You could either use gdb (set break point on grub_zfs_open and follow it) or simply add debugging output. Start with grub_zfs_open in grub-core/fs/zfs/zfs.c, add top level printf to see which branch is follow

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #4, bug #8 (project grub): What special options for debug output could I use with grub-fstest? Because I use (same as in my grub.cfg): grub-fstest /dev/ada0p2 ls /ROOT/working/freebsd@/boot/kernel/zfs.ko which behaves the same as in grub boot prompt.

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #3, bug #8 (project grub): The difference between ls (or completion) and "ls -l" is that the latter tries to open file. Can you reproduce it using grub-fstest? This would allow using debugger in user space. ___ Reply

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #2, bug #8 (project grub): As of today, it is the current GIT muster. It says:"up-to-date with origin/master". ___ Reply to this item at: _

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

Follow-up Comment #1, bug #8 (project grub): Obligatory question did you test with current GIT master? If yes, which commit? ___ Reply to this item at: __

[bug #44448] grub refuses to load (or recognize) a freebsd module -- "file not found"

URL: Summary: grub refuses to load (or recognize) a freebsd module -- "file not found" Project: GNU GRUB Submitted by: bergerkos Submitted on: Fri 06 Mar 2015 12:44:42 PM GMT Category: