[DragonFlyBSD - Bug #3057] (In Progress) HAMMER2 + new PFS + reboot
Issue #3057 has been updated by dillon. Status changed from New to In Progress Assignee set to dillon I fixed a number of PFS related bugs this afternoon where crashes could occur on (A) umount and (B) if you attempt to mount device@LABEL where LABEL does not exist. Update and keep watch. Multiple PFS mounting and unmounting has not been heavily tested yet and from your bug report there could be more issues. In particular, I have not come across the problem reported in your core.txt.4 where multiple chains are still active on the last umount... that's serious. Only the v-chain and the f-chain roots are supposed to still be active. I will start testing with more PFS's. Definitely keep updating this bug with PFS-related issues you come across. -Matt Bug #3057: HAMMER2 + new PFS + reboot http://bugs.dragonflybsd.org/issues/3057#change-13219 * Author: yellowrabbit2010 * Status: In Progress * Priority: Normal * Assignee: dillon * Category: * Target version: Hello, The situation is like this: I create PFS on mounted HAMMER2 (tryed with mounted LOCAL or ROOT), copy several files there and turn off the machine by `shutdown -p now'. Here is crash #4 (four because of previuos 0-3 are the same - I made about ten PFSes:) ) ---Files core.txt.4 (164 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3056] HAMMER2 corruption - nonexistent files
Issue #3056 has been updated by dillon. I hit the cluster_write() crash too, and it should now be fixed in master. It turned out to be a bug in devfs that only hammer2 tickles due to the way hammer2 uses cluster_write(). Also fixed a number of other issues this morning (see the git logs), including a corruption bug that can triggered by a crash or panic. -Matt Bug #3056: HAMMER2 corruption - nonexistent files http://bugs.dragonflybsd.org/issues/3056#change-13218 * Author: arc...@b1t.name * Status: Feedback * Priority: Normal * Assignee: dillon * Category: Kernel * Target version: After one crash (like a week ago) I got one dir damaged: > find . | wc -l 144 > find . -type f |& wc -l 142 > find . … ./standard/module.time.9.cfg ./standard/module.notification.3.cfg ./standard/e_bindings.6.cfg ./standard/module.gadman.3.cfg ./standard/systray.5.cfg ./standard/module.tasks.5.cfg ./standard/e_bryces.5.cfg … > find . -type f … find: ./standard/module.conf.9.cfg: No such file or directory find: ./standard/module.music_control.7.cfg: No such file or directory find: ./standard/module.everything-apps.3.cfg: No such file or directory find: ./standard/module.ibar.7.cfg: No such file or directory find: ./standard/module.syscon.6.cfg: No such file or directory … No messages on system console even with vfs.hammer2.debug=1. Not fixed with cleanup/blukfree. Current kernel: 2e8a93d8402e. ---Files core.txt.31 (210 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3061] HAMMER2. Hang up, reboot, and crash.
Issue #3061 has been updated by yellowrabbit2010. Updated, reinstalled, recreate all PFSes, so far all is good. Except that I once again ran into http://bugs.dragonflybsd.org/issues/3057 :) I'll watch another couple of days. Bug #3061: HAMMER2. Hang up, reboot, and crash. http://bugs.dragonflybsd.org/issues/3061#change-13217 * Author: yellowrabbit2010 * Status: New * Priority: Normal * Assignee: dillon * Category: * Target version: I started the build as -- nice -n 9 make -j 8 buildworld -- @USR-SRC is mounted at /usr/scr, @USR-OBJ is mounted at /usr/obj. The compilation stalled, I pressed reset and after reboot the system dumped immediately. After that I was able to boot, but the PFSes were gone. Each attempt to mount any of them led to the following errors: --- Sep 19 17:23:31 fly kernel: hammer2_mount Sep 19 17:23:31 fly kernel: hammer2_mount: dev="/dev/serno/WD-WCC2EP295836.s1d" label="USR-OBJ" rdonly=0 Sep 19 17:23:31 fly kernel: hammer2: using volume header #3 Sep 19 17:23:31 fly kernel: alloc spmp 0xff8525bc tid c00b Sep 19 17:23:31 fly kernel: chain 0068a0f4480a.01 key= meth=31 CHECK FAIL (flags=00144002, bref/data f84c9b21bc9ef301/1e55118462e960c9) Sep 19 17:23:31 fly kernel: hammer2_mount: error Check Error reading super-root Sep 19 17:23:31 fly kernel: hammer2_unmount hmp=0xff852613a000 mount_count=0 Sep 19 17:23:31 fly kernel: unmount hmp 0xff852613a000 remove spmp 0xff8525bc Sep 19 17:23:31 fly kernel: unmount hmp 0xff852613a000 last ref to PMP=0xff8525bc Sep 19 17:23:31 fly kernel: pfsfree: 0xff8525bc lrucount=0 Sep 19 17:23:31 fly kernel: hammer2_unmount(A): devvp /dev/serno/WD-WCC2EP295836.s1d rbdirty 0 ronly=0 Sep 19 17:23:31 fly kernel: hammer2_unmount(B): devvp /dev/serno/WD-WCC2EP295836.s1d rbdirty 0 Sep 19 17:23:31 fly kernel: v-chain 0xff852613a4c0.255 /0 mir=c00b Sep 19 17:23:31 fly kernel: [2000] (?) refs=1 Sep 19 17:23:31 fly kernel: f-chain 0xff852613a640.254 /0 mir=c00a Sep 19 17:23:31 fly kernel: [0004] (?) refs=0 --- ---Files core.txt.0 (239 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2917] da8: reading primary partition table: error accessing offset 000000000000 for 512
Issue #2917 has been updated by liweitianux. ollehar wrote: > liweitianux wrote: > > I think I found this bug is related to the "ehci" driver in DFly. > > > > I took some efforts to make DFly run on my X220. Then I try to read the > > USB (2.0) stick from it, but it doesn't work with "ehci" driver loaded. > > How did you manage to boot dfly without the ehci driver? I'm facing this > exact problem with my X220. In fact, it took me quite some effort to install DFly on my X200 (also X220), then I managed to find that this issue is in the "ehci" driver from the installed DFly system (I can kldload and kldunload the "ehci" and "xhci" drivers and check the logging messages). By reading the loader(8) man page, there is a description on how to disable the auto loading of "ehci" (USB2.0) driver: go to the loader prompt, and input: -- lunset ehci_load set hint.ehci.0.disabled=1 -- WARNING: This issue of course exists in the installed DFly system, thus you can only work with the slow "ohci" (USB1.1) driver on X200/X220. NOTE: I tried install FreeBSD and OpenBSD on my X200 (X220 should be similar), and both of them works well (w.r.t. the USB2.0 driver). However, DFly runs much faster compared to them, especially to OpenBSD. Cheers, Aly Bug #2917: da8: reading primary partition table: error accessing offset for 512 http://bugs.dragonflybsd.org/issues/2917#change-13216 * Author: liweitianux * Status: New * Priority: Normal * Assignee: * Category: Driver * Target version: Hello, Recently, I tried to install DragonFly BSD on my old ThinkPad X200 with both the 20160512-snapshot and 4.4.3-release USB image. However, DragonFly failed to mount root from the USB device. I enabled the verbose boot, and got the following error message: (da8:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da8:umass-sim0:0:0:0): Retrying Command ... (da8:umass-sim0:0:0:0): error 5 (da8:umass-sim0:0:0:0): Retries Exhausted da8: reading primary partition table: error accessing offset for 512 Mounting root from ufs:da8s1a no disk named 'da8s1a' setrootbyname failed ffs_mountroot: can't find rootvp kthread 0xffe02050d700 syncer3 has exited Root mount failed: 6 And there does not exist the 'da8s1a' device when listing: mountroot> ? Possibly valid devices for root FS: "vn0" "vn1" "vn2" "vn3" "md0" "md0s0" "sg8" "sg0" "da8" "da0" "da0s1" "da0s2" "da0s5" "da0s6" "da0s7" "mapper/control" I also tried to disable the "xhci" load, but the same issue remained. On the other hand, I tried to install FreeBSD (11-current) on that laptop and succeeded. And I can read the same USB device (with the DragonFly image dd'd into it) under FreeBSD (with the "geom_part_bsd64" module loaded). P.S.: I noticed there already existed a related bug report #2822 with this similar issue. But I think this bug may not related with the USB3.0, but very likely due to the CAM, and that bug stalls for a long time. Therefore I decide to open a new bug report. It's my pleasure to provide any further information if necessary. Best regards! Aly -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2917] da8: reading primary partition table: error accessing offset 000000000000 for 512
Issue #2917 has been updated by ollehar. liweitianux wrote: > I think I found this bug is related to the "ehci" driver in DFly. > > I took some efforts to make DFly run on my X220. Then I try to read the USB > (2.0) stick from it, but it doesn't work with "ehci" driver loaded. How did you manage to boot dfly without the ehci driver? I'm facing this exact problem with my X220. Bug #2917: da8: reading primary partition table: error accessing offset for 512 http://bugs.dragonflybsd.org/issues/2917#change-13215 * Author: liweitianux * Status: New * Priority: Normal * Assignee: * Category: Driver * Target version: Hello, Recently, I tried to install DragonFly BSD on my old ThinkPad X200 with both the 20160512-snapshot and 4.4.3-release USB image. However, DragonFly failed to mount root from the USB device. I enabled the verbose boot, and got the following error message: (da8:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da8:umass-sim0:0:0:0): Retrying Command ... (da8:umass-sim0:0:0:0): error 5 (da8:umass-sim0:0:0:0): Retries Exhausted da8: reading primary partition table: error accessing offset for 512 Mounting root from ufs:da8s1a no disk named 'da8s1a' setrootbyname failed ffs_mountroot: can't find rootvp kthread 0xffe02050d700 syncer3 has exited Root mount failed: 6 And there does not exist the 'da8s1a' device when listing: mountroot> ? Possibly valid devices for root FS: "vn0" "vn1" "vn2" "vn3" "md0" "md0s0" "sg8" "sg0" "da8" "da0" "da0s1" "da0s2" "da0s5" "da0s6" "da0s7" "mapper/control" I also tried to disable the "xhci" load, but the same issue remained. On the other hand, I tried to install FreeBSD (11-current) on that laptop and succeeded. And I can read the same USB device (with the DragonFly image dd'd into it) under FreeBSD (with the "geom_part_bsd64" module loaded). P.S.: I noticed there already existed a related bug report #2822 with this similar issue. But I think this bug may not related with the USB3.0, but very likely due to the CAM, and that bug stalls for a long time. Therefore I decide to open a new bug report. It's my pleasure to provide any further information if necessary. Best regards! Aly -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3060] (Closed) sys/boot/common/module.c:247: logical fault ?
Issue #3060 has been updated by swildner.
Status changed from New to Closed
Fix pushed, thanks!
Bug #3060: sys/boot/common/module.c:247: logical fault ?
http://bugs.dragonflybsd.org/issues/3060#change-13214
* Author: dcb
* Status: Closed
* Priority: Normal
* Assignee:
* Category:
* Target version:
dragonfly/sys/boot/common/module.c:247] ->
[dragonfly/sys/boot/common/module.c:254]: (warning) Identical condition
'got==0', second condition is always false
Source code is
got = read(fd, buf, 8192);
if (got == 0)
break;
if (got < 0) {
printf("error reading '%s': %s\n",
name, strerror(errno));
break;
}
if (got == 0)
crc = iscsi_crc32(buf, got);
else
crc = iscsi_crc32_ext(buf, got, crc);
So it looks like the crc code is never executed.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3061] HAMMER2. Hang up, reboot, and crash.
Issue #3061 has been updated by dillon. Assignee set to dillon I think I may have fixed this one last night in master (commit id through to a964af6f47472). I also believe that the stall should be fixed too (19808ac9def). There was a bug in the flush code that could catch some indirect block management in the middle of moving elements into or out of an indirect block, causing a damaged topology to be committed to media. This bug self-corrected during a normal shutdown, halt, or reboot, but not if the machine crashes or undergoes a hard reset. Unfortunately, once damaged, the topology pretty much can't be repaired and the filesystem needs to be newfs_hammer2'd. So I would say, update, reinstall, and keep watch. If it happens again with a kernel with a commitid of a964af6f47472 or later then we need to look at it more closely. -Matt Bug #3061: HAMMER2. Hang up, reboot, and crash. http://bugs.dragonflybsd.org/issues/3061#change-13213 * Author: yellowrabbit2010 * Status: New * Priority: Normal * Assignee: dillon * Category: * Target version: I started the build as -- nice -n 9 make -j 8 buildworld -- @USR-SRC is mounted at /usr/scr, @USR-OBJ is mounted at /usr/obj. The compilation stalled, I pressed reset and after reboot the system dumped immediately. After that I was able to boot, but the PFSes were gone. Each attempt to mount any of them led to the following errors: --- Sep 19 17:23:31 fly kernel: hammer2_mount Sep 19 17:23:31 fly kernel: hammer2_mount: dev="/dev/serno/WD-WCC2EP295836.s1d" label="USR-OBJ" rdonly=0 Sep 19 17:23:31 fly kernel: hammer2: using volume header #3 Sep 19 17:23:31 fly kernel: alloc spmp 0xff8525bc tid c00b Sep 19 17:23:31 fly kernel: chain 0068a0f4480a.01 key= meth=31 CHECK FAIL (flags=00144002, bref/data f84c9b21bc9ef301/1e55118462e960c9) Sep 19 17:23:31 fly kernel: hammer2_mount: error Check Error reading super-root Sep 19 17:23:31 fly kernel: hammer2_unmount hmp=0xff852613a000 mount_count=0 Sep 19 17:23:31 fly kernel: unmount hmp 0xff852613a000 remove spmp 0xff8525bc Sep 19 17:23:31 fly kernel: unmount hmp 0xff852613a000 last ref to PMP=0xff8525bc Sep 19 17:23:31 fly kernel: pfsfree: 0xff8525bc lrucount=0 Sep 19 17:23:31 fly kernel: hammer2_unmount(A): devvp /dev/serno/WD-WCC2EP295836.s1d rbdirty 0 ronly=0 Sep 19 17:23:31 fly kernel: hammer2_unmount(B): devvp /dev/serno/WD-WCC2EP295836.s1d rbdirty 0 Sep 19 17:23:31 fly kernel: v-chain 0xff852613a4c0.255 /0 mir=c00b Sep 19 17:23:31 fly kernel: [2000] (?) refs=1 Sep 19 17:23:31 fly kernel: f-chain 0xff852613a640.254 /0 mir=c00a Sep 19 17:23:31 fly kernel: [0004] (?) refs=0 --- ---Files core.txt.0 (239 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3056] (Feedback) HAMMER2 corruption - nonexistent files
Issue #3056 has been updated by arc...@b1t.name. Status changed from Resolved to Feedback Oops, it's not over yet. I hadn't paid attention to other fs parts and some wrong files were still present. I cleaned up whole disk from incorrect files (god bless backups) and found some more weird things: -rw-r--r-- 1 rootwheel 4 19-Sep-2017 19:23 slim.pid -rw-r--r-- 1 rootwheel 4 19-Sep-2017 19:23 slim.pid -rw-r--r-- 1 rootwheel 4 19-Sep-2017 19:23 slim.pid -rw-r--r-- 1 rootwheel 4 19-Sep-2017 19:23 slim.pid -rw--- 1 rootwheel 4 19-Sep-2017 19:23 smartd.pid -rw--- 1 rootwheel 4 19-Sep-2017 19:23 smartd.pid -rw--- 1 rootwheel 4 19-Sep-2017 19:23 smartd.pid -rw--- 1 rootwheel 4 19-Sep-2017 19:23 smartd.pid -rw--- 1 rootwheel 3 19-Sep-2017 19:22 syslog.pid -rw--- 1 rootwheel 3 19-Sep-2017 19:22 syslog.pid -rw--- 1 rootwheel 3 19-Sep-2017 19:22 syslog.pid -rw--- 1 rootwheel 3 19-Sep-2017 19:22 syslog.pid If I do `hammer2 destroy filename` one of them is destroyed. I also noticed that after the crash simple empty files may appear in the place of newly created files. Will clean up the drive and check how it would work. Bug #3056: HAMMER2 corruption - nonexistent files http://bugs.dragonflybsd.org/issues/3056#change-13212 * Author: arc...@b1t.name * Status: Feedback * Priority: Normal * Assignee: dillon * Category: Kernel * Target version: After one crash (like a week ago) I got one dir damaged: > find . | wc -l 144 > find . -type f |& wc -l 142 > find . … ./standard/module.time.9.cfg ./standard/module.notification.3.cfg ./standard/e_bindings.6.cfg ./standard/module.gadman.3.cfg ./standard/systray.5.cfg ./standard/module.tasks.5.cfg ./standard/e_bryces.5.cfg … > find . -type f … find: ./standard/module.conf.9.cfg: No such file or directory find: ./standard/module.music_control.7.cfg: No such file or directory find: ./standard/module.everything-apps.3.cfg: No such file or directory find: ./standard/module.ibar.7.cfg: No such file or directory find: ./standard/module.syscon.6.cfg: No such file or directory … No messages on system console even with vfs.hammer2.debug=1. Not fixed with cleanup/blukfree. Current kernel: 2e8a93d8402e. ---Files core.txt.31 (210 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3056] (Resolved) HAMMER2 corruption - nonexistent files
Issue #3056 has been updated by arc...@b1t.name. File core.txt.31 added Status changed from In Progress to Resolved Today I tested hammer2 destroy and it worked fine, yet 5 minutes later host crashed with (attached coredump). Host was actually crashing again with attempts to write that crash to /var/crash (with the same traceback). Probably unrelated. Bug #3056: HAMMER2 corruption - nonexistent files http://bugs.dragonflybsd.org/issues/3056#change-13211 * Author: arc...@b1t.name * Status: Resolved * Priority: Normal * Assignee: dillon * Category: Kernel * Target version: After one crash (like a week ago) I got one dir damaged: > find . | wc -l 144 > find . -type f |& wc -l 142 > find . … ./standard/module.time.9.cfg ./standard/module.notification.3.cfg ./standard/e_bindings.6.cfg ./standard/module.gadman.3.cfg ./standard/systray.5.cfg ./standard/module.tasks.5.cfg ./standard/e_bryces.5.cfg … > find . -type f … find: ./standard/module.conf.9.cfg: No such file or directory find: ./standard/module.music_control.7.cfg: No such file or directory find: ./standard/module.everything-apps.3.cfg: No such file or directory find: ./standard/module.ibar.7.cfg: No such file or directory find: ./standard/module.syscon.6.cfg: No such file or directory … No messages on system console even with vfs.hammer2.debug=1. Not fixed with cleanup/blukfree. Current kernel: 2e8a93d8402e. ---Files core.txt.31 (210 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3060] sys/boot/common/module.c:247: logical fault ?
Issue #3060 has been updated by lubos.
I think the second condition should be checking `crc' instead, like this:
diff --git a/sys/boot/common/module.c b/sys/boot/common/module.c
index 449e64d..24ff89e 100644
--- a/sys/boot/common/module.c
+++ b/sys/boot/common/module.c
@@ -251,7 +251,7 @@ command_crc(int argc, char *argv[])
name, strerror(errno));
break;
}
- if (got == 0)
+ if (crc == 0)
crc = iscsi_crc32(buf, got);
else
crc = iscsi_crc32_ext(buf, got, crc);
Bug #3060: sys/boot/common/module.c:247: logical fault ?
http://bugs.dragonflybsd.org/issues/3060#change-13210
* Author: dcb
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
dragonfly/sys/boot/common/module.c:247] ->
[dragonfly/sys/boot/common/module.c:254]: (warning) Identical condition
'got==0', second condition is always false
Source code is
got = read(fd, buf, 8192);
if (got == 0)
break;
if (got < 0) {
printf("error reading '%s': %s\n",
name, strerror(errno));
break;
}
if (got == 0)
crc = iscsi_crc32(buf, got);
else
crc = iscsi_crc32_ext(buf, got, crc);
So it looks like the crc code is never executed.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3059] sbin/camcontrol/camcontrol.c: pointless code ?
Issue #3059 has been updated by lubos. Perhaps assignment to `error' is missing? Like this: diff --git a/sbin/camcontrol/camcontrol.c b/sbin/camcontrol/camcontrol.c index 0fef6e5..1b98c47 100644 --- a/sbin/camcontrol/camcontrol.c +++ b/sbin/camcontrol/camcontrol.c @@ -689,7 +689,7 @@ scsidoinquiry(struct cam_device *device, int argc, char **argv, return(error); if (arglist & CAM_ARG_GET_SERIAL) - scsiserial(device, retry_count, timeout); + error = scsiserial(device, retry_count, timeout); if (error != 0) return(error); Bug #3059: sbin/camcontrol/camcontrol.c: pointless code ? http://bugs.dragonflybsd.org/issues/3059#change-13209 * Author: dcb * Status: New * Priority: Low * Assignee: * Category: * Target version: dragonfly/sbin/camcontrol/camcontrol.c:688] -> [dragonfly/sbin/camcontrol/camcontrol.c:694]: (warning) Identical condition 'error!=0', second condition is always false Source code is if (error != 0) return(error); if (arglist & CAM_ARG_GET_SERIAL) scsiserial(device, retry_count, timeout); if (error != 0) return(error); -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3061] (New) HAMMER2. Hang up, reboot, and crash.
Issue #3061 has been reported by yellowrabbit2010. Bug #3061: HAMMER2. Hang up, reboot, and crash. http://bugs.dragonflybsd.org/issues/3061 * Author: yellowrabbit2010 * Status: New * Priority: Normal * Assignee: * Category: * Target version: I started the build as -- nice -n 9 make -j 8 buildworld -- @USR-SRC is mounted at /usr/scr, @USR-OBJ is mounted at /usr/obj. The compilation stalled, I pressed reset and after reboot the system dumped immediately. After that I was able to boot, but the PFSes were gone. Each attempt to mount any of them led to the following errors: --- Sep 19 17:23:31 fly kernel: hammer2_mount Sep 19 17:23:31 fly kernel: hammer2_mount: dev="/dev/serno/WD-WCC2EP295836.s1d" label="USR-OBJ" rdonly=0 Sep 19 17:23:31 fly kernel: hammer2: using volume header #3 Sep 19 17:23:31 fly kernel: alloc spmp 0xff8525bc tid c00b Sep 19 17:23:31 fly kernel: chain 0068a0f4480a.01 key= meth=31 CHECK FAIL (flags=00144002, bref/data f84c9b21bc9ef301/1e55118462e960c9) Sep 19 17:23:31 fly kernel: hammer2_mount: error Check Error reading super-root Sep 19 17:23:31 fly kernel: hammer2_unmount hmp=0xff852613a000 mount_count=0 Sep 19 17:23:31 fly kernel: unmount hmp 0xff852613a000 remove spmp 0xff8525bc Sep 19 17:23:31 fly kernel: unmount hmp 0xff852613a000 last ref to PMP=0xff8525bc Sep 19 17:23:31 fly kernel: pfsfree: 0xff8525bc lrucount=0 Sep 19 17:23:31 fly kernel: hammer2_unmount(A): devvp /dev/serno/WD-WCC2EP295836.s1d rbdirty 0 ronly=0 Sep 19 17:23:31 fly kernel: hammer2_unmount(B): devvp /dev/serno/WD-WCC2EP295836.s1d rbdirty 0 Sep 19 17:23:31 fly kernel: v-chain 0xff852613a4c0.255 /0 mir=c00b Sep 19 17:23:31 fly kernel: [2000] (?) refs=1 Sep 19 17:23:31 fly kernel: f-chain 0xff852613a640.254 /0 mir=c00a Sep 19 17:23:31 fly kernel: [0004] (?) refs=0 --- ---Files core.txt.0 (239 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
