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
