Date: Tue, 03 Mar 2015 17:17:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198231] [unionfs] deadlock Message-ID: <bug-198231-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198231 Bug ID: 198231 Summary: [unionfs] deadlock Product: Base System Version: 9.3-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: andre@fbsd.ata.myota.org I can reliably deadlock a 9.3-STABLE by the following procedure: Let's assume that /tmp is a standard swap-backed file system already. First let's set up what we need: mkdir /tmp/1 /tmp/2 mount -v -t unionfs /tmp/1 /usr/local mount -v -t unionfs /tmp/2 /usr/local No let's lock the system: mkdir /tmp/2/bla while :; do echo go tar -cC /usr/src/etc -f - . | tar -xpC /tmp/2/bla -f - done It survives about 3 or 4 rounds, sometimes more, sometimes only 2. It is important to use tar to copy the stuff. If we replace the tar line by e.g. cp -pR /usr/src/etc/* /tmp/2/bla things are all well. The system doesn't lock up entirely, you can move the mouse and ping it but no fs access is possible anymore. One can switch to the console and enter the debugger but a reboot with ctrl-alt-del doesn't work... The interesting part is that all this worked pretty well on 9-STABLE until approx. 2 months ago. But nothing had been committed to unionfs for a long time so I really have no idea what's going on. It also reminds us of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161511 but this stuff had been merged to 9-STABLE already... -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198231-8>