From owner-freebsd-fs@FreeBSD.ORG Fri Dec 6 12:14:15 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D413383E for ; Fri, 6 Dec 2013 12:14:15 +0000 (UTC) Received: from pi.nmdps.net (pi.nmdps.net [IPv6:2a01:be00:10:201:0:80:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 2F95816B4 for ; Fri, 6 Dec 2013 12:14:14 +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 D9A08138B; Fri, 6 Dec 2013 13:14:11 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 06 Dec 2013 13:14:09 +0100 From: krichy@cflinux.hu To: Steven Hartland Subject: Re: zfs deadlock In-Reply-To: <95E8158BD748482F8CE2EEA040990138@multiplay.co.uk> References: <2D9058D8E6F9483CA1A6C78A2DA6E71B@multiplay.co.uk> <26807186f152d97fe54c4f0e6f888275@cflinux.hu> <9afe86004abc6e172e57e54d8e7f9d7f@cflinux.hu> <8f0b7b49d7cba1c48d98895eb0a46abd@cflinux.hu> <95E8158BD748482F8CE2EEA040990138@multiplay.co.uk> Message-ID: <40b6d20f62013978b4c3d861c3d323db@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Dec 2013 12:14:15 -0000 But that causes a kernel panic. And even a user on the system can change directory to a snapshot dir, so then he may force the system to crash? 2013-12-06 11:35 időpontban Steven Hartland ezt írta: > Thats correct it unmounts the mounted snapshot. > > Regards > Steve > > ----- Original Message ----- From: > To: "Steven Hartland" > Cc: > Sent: Friday, December 06, 2013 8:50 AM > Subject: Re: zfs deadlock > > >> 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" >>>>> >>>>> To: >>>>> 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. >> > > > ================================================ > 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.