Date: Fri, 06 Dec 2013 13:17:01 +0100 From: krichy@cflinux.hu To: freebsd-fs@freebsd.org Subject: Re: zfs deadlock Message-ID: <7f6eb8802dff234dc7dc516b9bdbcc03@cflinux.hu> In-Reply-To: <95E8158BD748482F8CE2EEA040990138@multiplay.co.uk> References: <alpine.BSF.2.00.1312051548410.80538@pi.nmdps.net> <2D9058D8E6F9483CA1A6C78A2DA6E71B@multiplay.co.uk> <26807186f152d97fe54c4f0e6f888275@cflinux.hu> <9afe86004abc6e172e57e54d8e7f9d7f@cflinux.hu> <8f0b7b49d7cba1c48d98895eb0a46abd@cflinux.hu> <95E8158BD748482F8CE2EEA040990138@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
I've applied r258294 on top of releng/9.2, and using the attached scripts parallel, the system got into a deadlock again. 2013-12-06 11:35 időpontban Steven Hartland ezt írta: > Thats correct it unmounts the mounted snapshot. > > Regards > Steve > > ----- Original Message ----- From: <krichy@cflinux.hu> > To: "Steven Hartland" <killing@multiplay.co.uk> > Cc: <freebsd-fs@freebsd.org> > 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" >>>>> <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. >> > > > ================================================ > 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 15:06:12 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 D75A0331 for <freebsd-fs@freebsd.org>; Fri, 6 Dec 2013 15:06:12 +0000 (UTC) Received: from nm9-vm0.bullet.mail.bf1.yahoo.com (nm9-vm0.bullet.mail.bf1.yahoo.com [98.139.213.154]) by mx1.freebsd.org (Postfix) with SMTP id 77EB81520 for <freebsd-fs@freebsd.org>; Fri, 6 Dec 2013 15:06:12 +0000 (UTC) Received: from [98.139.212.153] by nm9.bullet.mail.bf1.yahoo.com with NNFMP; 06 Dec 2013 15:02:55 -0000 Received: from [98.139.213.11] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 06 Dec 2013 15:02:55 -0000 Received: from [127.0.0.1] by smtp111.mail.bf1.yahoo.com with NNFMP; 06 Dec 2013 15:02:55 -0000 X-Yahoo-Newman-Id: 910571.80117.bm@smtp111.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: u.4uETQVM1lSUBcOg9cTfBVrk2at7v0v3ioFaBknCh85V15 5csdx7Kq8NRMdJ9iuvW3rM_yfby7YkC7elCXyyLnJUdwyqkK6WseVggpfBbw oFdUIzs_qi6EXlO3VwCXhZMVGKZbcSvtqHT2u1SFBhU1cPCjk_hY0ioPfpJk wfbYjDn9zHgKSS5SoVPX1q2Xpz1y6zF8EL2Sd63nI3hRWUwoHMRFc9J4MWA2 jtCNOj9ms.DuqTZopa3yRWBVqo8YCJf2uPdqvUNvU0NdrZqmYNu7fQ.DgqAf yaK2cLuhYcMQgXJFcBdfZYpQ11fGeXvvyr6XEw_UR9U02BOSFxWV3DjA0fXR pbRADolvdC21pFTe2DgPsq9fjMkA6uWD1XfAUH9R6.SWGj0RU7RGQFUbWm5r DopUK3v50lOJNOok9V62g72VzjzBbrWJrnlndmwP8fufKlcIstt_0zLjGi5G DiYGZRPbNbx9oNtgJlsBxun9uezdKuypNy70.ns5YW6pLmoLGLFQ.vnD8qwU 61nWGS0axhIRTr7p9e5oWxM6HzZXSY.wW7AlHgtlmu8hmTJhJKBBhZIKHD5J z6Sn2iQ-- X-Yahoo-SMTP: hdvk3SuswBDjqWuLIhjJ7cQT_83YtZNiMmKQOSuhvZGxXQ-- X-Rocket-Received: from [192.168.1.105] (jas@99.238.41.227 with ) by smtp111.mail.bf1.yahoo.com with SMTP; 06 Dec 2013 07:02:55 -0800 PST Message-ID: <52A1E722.5070207@cse.yorku.ca> Date: Fri, 06 Dec 2013 10:02:58 -0500 From: Jason Keltz <jas@cse.yorku.ca> User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: masking filesystem mount References: <alpine.BSF.2.00.1312051548410.80538@pi.nmdps.net> <2D9058D8E6F9483CA1A6C78A2DA6E71B@multiplay.co.uk> <26807186f152d97fe54c4f0e6f888275@cflinux.hu> <9afe86004abc6e172e57e54d8e7f9d7f@cflinux.hu> <8f0b7b49d7cba1c48d98895eb0a46abd@cflinux.hu> <95E8158BD748482F8CE2EEA040990138@multiplay.co.uk> <7f6eb8802dff234dc7dc516b9bdbcc03@cflinux.hu> In-Reply-To: <7f6eb8802dff234dc7dc516b9bdbcc03@cflinux.hu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 15:06:13 -0000 Hi.. I'm using FreeBSD 9.2 system as a backup/archive pooling server. At the moment, one of the servers being backed up is a Linux file server. Assume that the file server has a directory "/export/home" which contains home directories, user1, user2, and user3. Every day, the file server is backed up to the pooling server creating a structure something like: /backup/home: user1/ user2/ user3/ Of course the best part is: /backup/home/.zfs/snapshot: day1/ day2/ day3 (then of course user1/ user2/ user3/ under each day) I'd like to automount the contents of a users snapshot directory onto a departmental system. However, I'd prefer if the user sees just their own files in their arc directory, and not everyone elses. That is, when user1 using one of our systems changes into say, /arc/user1, he should see: day1/ day2/ day3/ ... but when he goes into day1/ da2/ day3, he should see only his directory - not everyones. To make this happen, I wonder if there's a way to mount a whole filesystem, but somehow provide a "mask" that can be used to "hide" parts from view. In this case, if I could somehow specify a regexp like ^*/user1/* so that user1 sees only his files, this would be good. I think the answer is no, but it's an interesting "problem". (Yes, if I snapshotted each users home directory separately, there would be no problem). By the way -- one other question on the topic of ZFS snapshots. I notice that a question as to why you cannot do a "pwd" in a .zfs directory has been asked before... apparently pwd works works if you make .zfs visible (which I haven't tried since I don't want .zfs to be visible). My question is -- what is the technical reason this isn't possible? On the surface, sounds like something that should be easily to fix. Underneath, I guess it's more tricky... I just know it seems logical to me to be able to do a pwd in a .zfs directory whether .zfs is visible or not. Thanks.. Jason.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7f6eb8802dff234dc7dc516b9bdbcc03>