Date: Fri, 06 Dec 2013 09:03:23 +0100 From: krichy@cflinux.hu To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-fs@freebsd.org Subject: Re: zfs deadlock Message-ID: <9afe86004abc6e172e57e54d8e7f9d7f@cflinux.hu> In-Reply-To: <26807186f152d97fe54c4f0e6f888275@cflinux.hu> References: <alpine.BSF.2.00.1312051548410.80538@pi.nmdps.net> <2D9058D8E6F9483CA1A6C78A2DA6E71B@multiplay.co.uk> <26807186f152d97fe54c4f0e6f888275@cflinux.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear Steven, While I was playig with zfs, trying to reproduce the previous bug, accidentaly hit another one, which caused a trace I attached. The snapshot contains directories in 2 depth, which contain files. It was to simulate a vmail setup, with domain/user hierarchy. I hope it is useful for someone. I used the attached two scripts to reproduce the ZFS bug. It definetly crashes the system, in the last 10 minutes it is the 3rd time. Regards, 2013-12-05 20:26 időpontban krichy@cflinux.hu ezt írta: > Dear Steven, > > Thanks for your reply. Do you know how to reproduce the bug? Because > simply sending a snapshot which is mounted does not automatically > trigger the deadlock. Some special cases needed, or what? > How to prove that the patch fixes this? > > Regards, > 2013-12-05 19:39 időpontban Steven Hartland ezt írta: >> Known issue you want: >> http://svnweb.freebsd.org/changeset/base/258595 >> >> Regards >> Steve >> >> ----- Original Message ----- From: "Richard Kojedzinszky" >> <krichy@cflinux.hu> >> To: <freebsd-fs@freebsd.org> >> Sent: Thursday, December 05, 2013 2:56 PM >> Subject: zfs deadlock >> >> >>> Dear fs devs, >>> >>> We have a freenas server, which is basicaly a freebsd. I was trying >>> to look at snapshots using ls .zfs/snapshot/. >>> >>> When I issued it, the system entered a deadlock. An NFSD was running, >>> a zfs send was running when I issued the command. >>> >>> I attached to command outputs while the system was in a deadlock >>> state. I tried to issue >>> # reboot -q >>> But that did not restart the system. After a while (5-10 minutes) the >>> system rebooted, I dont know if the deadman caused that. >>> >>> Now the system is up and running. >>> >>> It is basically a freebsd 9.2 kernel. >>> >>> Do someone has a clue? >>> >>> Kojedzinszky Richard >> >> >> -------------------------------------------------------------------------------- >> >> >>> _______________________________________________ >>> freebsd-fs@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> >> ================================================ >> This e.mail is private and confidential between Multiplay (UK) Ltd. >> and the person or entity to whom it is addressed. In the event of >> misdirection, the recipient is prohibited from using, copying, >> printing or otherwise disseminating it or any information contained in >> it. >> >> In the event of misdirection, illegible or incomplete transmission >> please telephone +44 845 868 1337 >> or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Fri Dec 6 08:50:32 2013 Return-Path: <owner-freebsd-fs@FreeBSD.ORG> Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9FE4E9CE for <freebsd-fs@freebsd.org>; Fri, 6 Dec 2013 08:50:32 +0000 (UTC) Received: from pi.nmdps.net (pi.nmdps.net [109.61.102.5]) by mx1.freebsd.org (Postfix) with ESMTP id 1D413190E for <freebsd-fs@freebsd.org>; Fri, 6 Dec 2013 08:50:32 +0000 (UTC) Received: from pi.nmdps.net (localhost [127.0.0.1]) (Authenticated sender: krichy@cflinux.hu) by pi.nmdps.net (Postfix) with ESMTPSA id 337BA10F0; Fri, 6 Dec 2013 09:50:30 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 06 Dec 2013 09:50:27 +0100 From: krichy@cflinux.hu To: Steven Hartland <killing@multiplay.co.uk> Subject: Re: zfs deadlock In-Reply-To: <9afe86004abc6e172e57e54d8e7f9d7f@cflinux.hu> References: <alpine.BSF.2.00.1312051548410.80538@pi.nmdps.net> <2D9058D8E6F9483CA1A6C78A2DA6E71B@multiplay.co.uk> <26807186f152d97fe54c4f0e6f888275@cflinux.hu> <9afe86004abc6e172e57e54d8e7f9d7f@cflinux.hu> Message-ID: <8f0b7b49d7cba1c48d98895eb0a46abd@cflinux.hu> X-Sender: krichy@cflinux.hu User-Agent: Roundcube Webmail/0.9.5 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems <freebsd-fs.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>; List-Post: <mailto:freebsd-fs@freebsd.org> List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 06 Dec 2013 08:50:32 -0000 What is strange also, when a zfs send finishes, the paralell running find command issues errors: find: ./e/Chuje: No such file or directory find: ./e/singe: No such file or directory find: ./e/joree: No such file or directory find: ./e/fore: No such file or directory find: fts_read: No such file or directory Fri Dec 6 09:46:04 CET 2013 2 Seems if the filesystem got unmounted meanwhile. But the script is changed its working directory to the snapshot dir. Regards, 2013-12-06 09:03 időpontban krichy@cflinux.hu ezt írta: > Dear Steven, > > While I was playig with zfs, trying to reproduce the previous bug, > accidentaly hit another one, which caused a trace I attached. > > The snapshot contains directories in 2 depth, which contain files. It > was to simulate a vmail setup, with domain/user hierarchy. > > I hope it is useful for someone. > > I used the attached two scripts to reproduce the ZFS bug. > > It definetly crashes the system, in the last 10 minutes it is the 3rd > time. > > Regards, > 2013-12-05 20:26 időpontban krichy@cflinux.hu ezt írta: >> Dear Steven, >> >> Thanks for your reply. Do you know how to reproduce the bug? Because >> simply sending a snapshot which is mounted does not automatically >> trigger the deadlock. Some special cases needed, or what? >> How to prove that the patch fixes this? >> >> Regards, >> 2013-12-05 19:39 időpontban Steven Hartland ezt írta: >>> Known issue you want: >>> http://svnweb.freebsd.org/changeset/base/258595 >>> >>> Regards >>> Steve >>> >>> ----- Original Message ----- From: "Richard Kojedzinszky" >>> <krichy@cflinux.hu> >>> To: <freebsd-fs@freebsd.org> >>> Sent: Thursday, December 05, 2013 2:56 PM >>> Subject: zfs deadlock >>> >>> >>>> Dear fs devs, >>>> >>>> We have a freenas server, which is basicaly a freebsd. I was trying >>>> to look at snapshots using ls .zfs/snapshot/. >>>> >>>> When I issued it, the system entered a deadlock. An NFSD was >>>> running, a zfs send was running when I issued the command. >>>> >>>> I attached to command outputs while the system was in a deadlock >>>> state. I tried to issue >>>> # reboot -q >>>> But that did not restart the system. After a while (5-10 minutes) >>>> the system rebooted, I dont know if the deadman caused that. >>>> >>>> Now the system is up and running. >>>> >>>> It is basically a freebsd 9.2 kernel. >>>> >>>> Do someone has a clue? >>>> >>>> Kojedzinszky Richard >>> >>> >>> -------------------------------------------------------------------------------- >>> >>> >>>> _______________________________________________ >>>> freebsd-fs@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>>> To unsubscribe, send any mail to >>>> "freebsd-fs-unsubscribe@freebsd.org" >>> >>> ================================================ >>> This e.mail is private and confidential between Multiplay (UK) Ltd. >>> and the person or entity to whom it is addressed. In the event of >>> misdirection, the recipient is prohibited from using, copying, >>> printing or otherwise disseminating it or any information contained >>> in >>> it. >>> >>> In the event of misdirection, illegible or incomplete transmission >>> please telephone +44 845 868 1337 >>> or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9afe86004abc6e172e57e54d8e7f9d7f>