Re: VFS MFC testers wanted
Kris, For the record, we ran the following for about 30 minutes, with no ill effect: #!/bin/sh exec >> /var/log/panic exec 2>&1 echo echo `date` "-- trying to panic" while [ 1 ] do /sbin/mount /backup/ /bin/rm -rf /backup/foo /bin/cp -R /usr/bin /backup/foo /sbin/umount /backup/ echo -n '.' done At this point our plan is to cross our fingers and wait for 6.1. Thanks for all your efforts! chad Kris Kennaway wrote: On Tue, Mar 07, 2006 at 12:33:28PM -0500, Chad Whitacre wrote: Kris, Yes. FYI, I am fairly confident this is fixed, because I make extensive use of mount/umount+filesystem activity, and I am no longer seeing problems like this. Great! Thanks for the info. We won't kill ourselves trying to test this then. Well, I'd still like you to test it just to be sure. I'm not able to detect all FreeBSD bugs, after all (though I try :-) Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VFS MFC testers wanted
Kris, Yes. FYI, I am fairly confident this is fixed, because I make extensive use of mount/umount+filesystem activity, and I am no longer seeing problems like this. Great! Thanks for the info. We won't kill ourselves trying to test this then. chad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VFS MFC testers wanted
Kris, No, the rsync (i.e. activity on the filesystem) is important. Yeah, just ran a test w/o it actually. We are planning to run a test w/ some disk activity later this afternoon. I suppose the more activity, the more likely to see the bug, eh? chad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VFS MFC testers wanted
Jeff, Kris Kennaway directed me to this thread from FreeBSD-questions. I am seeing a "panic: unmount: dangling vnode" with 6.0-RELEASE. Here are the relevant threads: 2 probs w/ backup.sh: "Device busy" and "dangling vnode" http://lists.freebsd.org/pipermail/freebsd-questions/2006-March/114825.html "Panic: unmount: dangling vnode" http://lists.freebsd.org/pipermail/freebsd-questions/2006-March/115060.html If relevant, I may be able to test your patch, but the problem is occurring only rarely. Do you have any suggestions for isolating and reproducing this bug? Also, we are seeing this problem on a production box. I notice that the patch fixes 6 issues, and apparently "breaks the kernel ABI," which sounds nasty from out here in userland. Any chance of getting a patch that isolates this specific issue? I'll be more likely able to apply such a patch. Our alternative is to simply keep our backup drive always mounted until 6.1 comes out and test your patch then. :^) Thoughts? Thanks for your work on this. Chad Whitacre http://www.zetadev.com/ Jeff Roberson wrote: I plan to MFC all of this lovely stuff for 6.1: http://www.chesapeake.net/~jroberson/vfsmfc.diff I'm looking for people who are willing to patch their stable boxes and test this. This has the following changes in it: 1) Improved debugging with DEBUG_LOCKS via the new stack(9) api. 2) Fixed an INACTIVE leak. 3) Fixed several unmount races. 4) Fixed several nullfs unmount issues. 5) Some more Giant related VFS fixes and asserts. 6) Fixed the quota deadlock. These problems should be rare enough that most of you have not seen them. So just let me know if this introduces any new problems etc. I will be MFCing within a week. Thanks, Jeff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VFS MFC testers wanted
Kris, If relevant, I may be able to test your patch, but the problem is occurring only rarely. Do you have any suggestions for isolating and reproducing this bug? Run your script in a loop? And I assume I can meaningfully test w/o the rsync call? I.e., just mounting and unmounting the drive over and over again should trigger the error, no? chad ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
